Re: Adding reviewing to our development process

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi all,

Jeremy Katz wrote:
On Thu, 2008-10-23 at 10:40 +0200, Hans de Goede wrote:
So I've been thinking that we really need to change our processes to include a review phase for all patches except the most trivial ones (the ones fixing all the typos).


<snip>


It's something I've thought about from time to time as well.  We've
gotten better with sending larger patches to the list for review (though
there's still room for some improvement) which was really sort of a
first step.


<snip>


But that said, the goal would be that by having such pre-commit reviews,
we could hopefully reduce the number of times that we're blocking a
release tree.  So I definitely think it's worth trying.  The question
comes down to when do we start doing it:
1) Now
2) At the beginning of the F11 development cycle

Given the risk for slowing down a release that really has no room to be
slipped, I lean a little bit towards the latter.  But opinions to the
contrary  could easily sway me otherwise.  Especially if Jesse was
on-board.


I agree lets start doing this for F-11, I think we also need to write something up how the process will look (something like 10-20 lines of text, no prose please) does anyone have a suggestion how to shape this?

Regards,

Hans

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux