This is likely an artifact of the branch "freeze" between the last beta and the final. Which bugs were they? Are they in the Collector? In general, most bugfixes make it into both the trunk and the current release branch. ----- Original Message ----- From: <richard@bizarsoftware.com.au> To: "Shane Hathaway" <shane@digicool.com> Cc: <zope-dev@zope.org> Sent: Monday, April 30, 2001 7:16 PM Subject: Re: [Zope-dev] Heads up -- big changes on trunk
Shane Hathaway wrote:
This notice only applies to developers who are following the bleeding edge of Zope, the CVS trunk. It does not apply if you downloaded Zope from a web site.
As a broader issue, what's the story with bugfixes in the 2.3 branch? We've got a couple of patches in against 2.3 now that have been patched in the "trunk" but not in the 2.3 branch. We're not going to be moving to the bleeding edge any time soon, because our customers aren't going to like being forced to install a whole new Zope instance / python interpreter just to run our product! I think it's bad enough that we're forcing them to use a "bleeding edge" 2.3.2 release...
What say DC?
Richard
-- Richard Jones richard@bizarsoftware.com.au Senior Software Developer, Bizar Software (www.bizarsoftware.com.au)
_______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )