Am 01.04.2007 um 22:23 schrieb Christian Boos: > I'd like to propose a few steps to get us moving forward on the 0.11 > topic, as we're gradually getting to the feature set we wanted to > have. > A lot has already been done in the past 8 months, but there's > definitely > some work ahead of us. There are currently a few working branches that > could be integrated: > - genshi510 > - pycon/workflow > - security > - vc-refactoring > - pycon/render-filter > > In particular, there's genshi510 that could probably benefit a lot > to be > on the trunk, so that we can fix the remaining issues as we see them. > That was probably the initial intent of cmlenz when he did the changes > directly on trunk. The problem I had with this approach was that it > broke the usability status of trunk for an unspecified amount of time, > while there were a lot of people trying out trunk on the assumption > that it was stable enough for their needs. I didn't want to break this > assumption in people's mind, as I think it's actually a very good > thing > that we have people trying out trunk and willing to report the few > occasional issues they might stumble upon. So I moved those changes > on a > stabilization branch, and as a result the trunk was indeed usable > again > but the branch has stalled...
FYI, I consider it bad style to move someone else's changes to a "stabilization branch" without any kind of notice or dicussion on this list. I've put a lot of work into those changes, and while I may have missed some places, it would've been better to just fix those -- instead of the current situation, which is frankly obnoxious (relying on a version of a dependency that's neither release *nor* trunk). > So what I'd like to do instead is to release a 0.11beta1, as trunk > stands now, and let people know that they should use this if they want > to try out 0.11dev, because the trunk will become temporarily quite > "unstable". We'll then merge genshi510, then the workflow branch. One, > two, three weeks later at most, things will have settled down again > and > trunk will recover its "usable" status. Huh? That's not a beta. You can't postpone major changes like the addition of workflow to after a beta release. Either such changes are postponed to the next release, or the beta needs to wait until they're in. Anything else is not sane release management in my book. So, * -1 on releasing a beta without the genshi-related changes. * -1 also on releasing a beta without major scheduled enhancements such as the security or workflow, assuming they're scheduled for the final release. We'll need to stay honest here. Looking at your list of things you'd like to see in 0.11, it seems like a 0.11 release is still rather far way at this point. Putting out a beta version that's nowhere close to what "beta" traditionally means isn't going to help anyone. Cheers, Chris -- Christopher Lenz cmlenz at gmx.de http://www.cmlenz.net/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
