On Wed, 7 Apr 2010, PCMan wrote: > Previously we use rolling release model. The advantage of this model is: > 1. Most of the components are actually indepedent. Rolling release can > make sure all of the users get the latest components. > 2. As they are independent, there is no point in synchronize their release. > 3. In this way the release of some components will be blocked by > others if there are some major blockers.
In my opinion the per component release is the best tactic to use. It will pressure the release team and not the developers. If the team can use a working path and adhere to each other this is by far the most powerful way of doing. I think. With a "release schedule" per component it will be easier to track the changes needed and the developers for each component will be more in charge of their work and the planning of the future of "their" component - making it a better product because they can work on what they want to work on with out being forced in to doing things they don't like. > A major release can be done by distro makers such as Lubuntu, but > major release doesn't seem to be needed for our components, especially > when part of the components are borrowed from other projects, such as > openbox and leafpad. > But I agree that having major releases is better for promotion. I have no objection in genereal of being clear about what we do but with a upfront release process and good software I do not see that we really need the extra attention that might be gained. And ofc I am from the Debian camp as you all know - relase when ready =) -- brother ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
