| |||||||||||||
Android, forking, and control: CommunicationAndroid, forking, and control: CommunicationPosted Jun 7, 2011 17:55 UTC (Tue) by PaulMcKenney (subscriber, #9624)In reply to: Android, forking, and control: Communication by dgm Parent article: Android, forking, and control
And isn't this the problem that "extreme programming" and "agile methods" were supposed to solve? ;-)
(Log in to post comments)
Android, forking, and control: Communication Posted Jun 7, 2011 18:35 UTC (Tue) by dlang (✭ supporter ✭, #313) [Link]
kernel development is probably the best example of 'agile methods' that you can find.
there is no planned feature set for each release, instead each development team works on their set of features and when the merge window starts, anything that's ready gets pushed upstream.
but this only works if the development teams work on smallish features (or does their development in a way that gradually changes the result rather than big bang changes)
|
|||||||||||||