On Mon, Aug 17, 2009 at 9:33 AM, Sebastien Douche<sdou...@gmail.com> wrote: > On Fri, Aug 14, 2009 at 19:20, Jim Fulton<j...@zope.com> wrote: > > Hi Jim > >> - We need to create a test branch. >> >> - When a developer wants to update a project version, they check out >> the test branch, make a local version change and run the tests. If the >> tests pass the check the change into the test branch. >> >> - We maintain windows and linux buildbots (or equivalent) against both >> the test branch and trunk for Python 2.4, 2.5 and 2.6. >> >> - When buildbot tests pass on all platforms and Python versions, we >> merge tested changes to the trunk. Note that the buildbot output >> needs to record the svn revision # tested. >> >> Thoughts? > > 1. When the new system will be the default way?
When we all agree on it and maybe when the tests pass on all platforms (or maybe sooner). > 2. Can you list the steps needed by the new system? (co, bin/test,...) Not until we finalize some things. > 3. Do you want Py2.4 buildbot for Zope 2.5? Huh? We'll want buildbots for Python 2.4, 2.5, and 2.6 > Nota: I don't have Windows buildbot. Hopefully, someone else can help with that. Jim -- Jim Fulton _______________________________________________ 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 )