|
From: Ulf E. <ulf...@fa...> - 2005-09-08 21:20:58
|
* miah [2005-09-08 16:48]: > I realize manpower on this project is limited. Personally, I'd like to > see Devel Snapshots, and bugs fixed in whatever is currently marked as > stable, unless its such a huge bug that it would take a tremendous > amount of manpower to fix or its already fixed in the dev branch. Its > its something easily mergable to stable then push it back.. Some people > do use this software for production and wont run the devel versions, but > its good to have devel available for testing etc. It shouldn't be all that much development work to merge fixes from cvs head to a stable branch, but we would need more testing to see whether the fixes work as well there (maybe a little fix relies on something bigger that also needs to be merged before it works alright). Is anyone tracking the 1.0 branch? If not, would a 1.0.1 release candidate be needed to get any testing at all before it is declared as better than 1.0? Now you have something that requires time and efforts.. There is also such small things such as saying "Hey, I would like to see this fix on the stable branch as well. Any chance it can be back-ported?" when you see something interesting entering the cvs head. Silence is too easily seen as lack of interest.. and if no one shows interest in a stable branch it is much easier to not have one I too wish to see bug fix updates, but are we big enough to pull that through? What about the old list of bugs. Where can I find people to help sort out what is relevant today and what is not? http://sourceforge.net/tracker/?group_id=14939&atid=114939 /Ulf |