Re: * Debian Releases *
> >I think we have a problem with our release schedule.
> >
> >The way this seems to work is that 3 months go by, the release is announced,
> >and then everybody tries to decide what should go in it. The result is
> >a lot of confusion, and lot of rushing around, and probably not the best
> >"stable" release.
> >
> >So... I propose:
> >
> > - We make a list of all things that need to be done to the distribution
> > as a whole.
> >
> > - Anything that can be completed and tested quickly (i.e. 1-2 weeks)
> > should be done and 1.2 should be released.
> >
> > - Of what remains, we decide what can be done (and tested!) in 3 months
> > for the 1.3 release.
> >
> >Now, ideally this list would be maintained and enforced by the project
> >leader. (Sorry, Bruce :-).
>
> Someone should write some software for managing projects like this!
> Since we only rarely have need for "enforcement", the software should
> encourage collective agreement wrt the task list and work needing.
> Anyone know of any software like this?
Well, it's a bit premature, but I think we could donate access to our
"Coordinator" product when it's finished (end of November is the current
plan). For more info, see: http://www.verisim.com/coordinator/
Brian
( bcwhite@verisim.com )
-------------------------------------------------------------------------------
It's not the days in your life, but the life in your days that counts.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: