[Zope-dev] Re: Resolution of issue #2333 before next maintenance release(s)?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Hicks wrote: Hi, Apparently a maintenance release for 2.10 is imminent. Would it be possible for someone to review the report for issue #2333 @: http://www.zope.org/Collectors/Zope/2333. The fix provided there comes with a test. If it's deemed suitable, could someone with commit privileges apply the patches before the release is cut? If not, could they tell me what I need to do to have it accepted? I am in the process of landing the test and fix on the Five 1.3, 1.4, and 1.5 branches and the Five trunk. Question for Andreas / Stefan: would it be alright if I blow away the release tags for Five 1.3.9 / 1.5.4 pseudo-releases? No tarballs / release announcements were made, AFAIK, and the only clients are the svn:externals links in the Zope2 tree. OTherwise, I need to create new releases, and change the Zope2 links. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGf9+D+gerLs4ltQ4RApfyAJ9iO5Oi6J0hKodP3CSUgx7zBwAfFACfYjCs ZyLol6e9Ql7ni2t2b1idKvM= =MQn6 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Resolution of issue #2333 before next maintenance release(s)?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tres Seaver wrote: Tim Hicks wrote: Hi, Apparently a maintenance release for 2.10 is imminent. Would it be possible for someone to review the report for issue #2333 @: http://www.zope.org/Collectors/Zope/2333. The fix provided there comes with a test. If it's deemed suitable, could someone with commit privileges apply the patches before the release is cut? If not, could they tell me what I need to do to have it accepted? I am in the process of landing the test and fix on the Five 1.3, 1.4, and 1.5 branches and the Five trunk. Question for Andreas / Stefan: would it be alright if I blow away the release tags for Five 1.3.9 / 1.5.4 pseudo-releases? No tarballs / release announcements were made, AFAIK, and the only clients are the svn:externals links in the Zope2 tree. OTherwise, I need to create new releases, and change the Zope2 links. For the record, I chose the second path after thinking it over a bit. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGf/PO+gerLs4ltQ4RAkE/AJ9+jXiLsuFZ4glizdEJ51skUjxu8wCgrrdp I+Xczripu/k1W3zhYoxKB50= =8jOe -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Resolution of issue #2333 before next maintenance release(s)?
Tres Seaver wrote: Tres Seaver wrote: Tim Hicks wrote: Hi, Apparently a maintenance release for 2.10 is imminent. Would it be possible for someone to review the report for issue #2333 @: http://www.zope.org/Collectors/Zope/2333. The fix provided there comes with a test. If it's deemed suitable, could someone with commit privileges apply the patches before the release is cut? If not, could they tell me what I need to do to have it accepted? I am in the process of landing the test and fix on the Five 1.3, 1.4, and 1.5 branches and the Five trunk. Question for Andreas / Stefan: would it be alright if I blow away the release tags for Five 1.3.9 / 1.5.4 pseudo-releases? No tarballs / release announcements were made, AFAIK, and the only clients are the svn:externals links in the Zope2 tree. OTherwise, I need to create new releases, and change the Zope2 links. For the record, I chose the second path after thinking it over a bit. Thanks for seeing to this! Tim ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
