Am Montag, 29. September 2003 01:34 schrieb James Sparenberg:
> On Sun, 2003-09-28 at 01:19, Warly wrote:
> > It may be a good idea, before cooker opens again, to take these
> > days to have some brainstorm.
> >
> > May you give your opinion on :
> >
> > - What was wrong in 9.2 development process?
> >
> > - We though a bit late in the 9.2 developement process to split
> > cooker ml, we should do it now.
> >
> > - What could we do to improve 9.3/10.0 development.
> >
> > - What should we do to improve the Wiki.
> >
> > - Should we have cooker snapshot ISOs?
> >
> > - What could we do, as a community, to increase the acceptance of
> > mandrakelinux?
> >
> > - How to have more contributors?
> >
> > And anything related to the mandrakelinux distro.
>
> In answer to all of the above.  How about splitting the development
> along 2 lines.  Mandrake tools and packages.  The idea here from my
> thought is that these really are two separate areas, with separate
> goals.

100% agree of this

> The next step would be to make the development of tools a continues
> project rather than a point/major release function.  Create a fourth
> area called testing on the mirrors.  This area differs from updates
> in that it isn't a bug fix but a known alpha product that is based on
> a stable release (in this case 9.2) and those power users who chose
> to can participate in the continuous testing of new ideas and
> directions. 

Yep. And this way people could test some things on stable release for 
cooker. Some of us have hard times to follow cooker, for testing 
mandrake tools this should really be affordable for a lot more people 
and have more testers because of that. 

>
> Finally when the MDK team chooses the final tool set from updates and
> this area, they become the tool set for the next release and then the
> crunch time would be able to concentrate on packages.  Overall it
> would yield a much more stable release process IMHO.

That idea is the best idea i have read during the whole thread. This 
would also help i18n people in translating, as translating could be 
done and tested during the whole time. 


I absolutly vote for this split up of development. 

Steffen

Reply via email to