On Tuesday 26 October 2004 09:07 pm, Anthony Baxter wrote: > As far as the original point (branching at the beta point, rather > than post-final-release) - I've seen little demand for making > this happen, and it increases both the workload and (much more > importantly) the chance for a visit from Mr Cockup. But it's Indeed it does. We don't need that. > something we could do now if there's a real groundswell of > people who want to get stuff into the trunk for 2.5 that extra > month early <wink>. As someone who works daily using the Zope 3 Way, I don't think it makes much sense for Python. No matter how easy Subversion makes moving patches around, it is another opportunity for a screwup. I don't see any reason to make the branch earlier than the first release candidate. We don't have a history of accidental inclusion of new features; when we've added things, it was done intentionally. (I'm not endorsing a policy on *that* here, just noting that we don't have a problem caused by the lack of an early branch.) > beta2: Wednesday, November 3rd > RC1: Wednesday, November 18th > final: Tuesday, November 30th This looks good for me at this point. -Fred -- Fred L. Drake, Jr. <fred at zope.com> Zope Corporation
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4