Hey, Wolfgang Schnerring wrote: [snip] > After we reach a consensus on how to do it (I'm in favor of the way > outlined above, of course ;-), I'd like to add a step-by-step > walkthrough of the day-to-day development of a package somewhere below > <http://docs.zope.org/zopetoolkit/process/index.html>, which would > include a description of how to run KGS tests.
That'd be awesome! > Regarding the KGS, I have a question: Where is the current KGS and how > do we update it? For the Zope Toolkit, I don't think it exists yet. There's a Zope 3.4 KGS and I know Stephan also mentioned wanting to make a 'wide KGS' that includes a lot more packages than what's in the ZTK (this can expand on the ZTK KGS though). For Grok, we maintain a versions.cfg list in the Grok trunk. > By "where is" I mean the location of the versions.cfg, > by "current" I mean the "trunk", the version currently in development, > the version where we probably want to bump the version number of a > package as soon as a version is released, > and by "update" I mean that I'd like this operation to involve no manual > interaction other than committing the new version number to SVN. I'd like to see such a method of working too. Regards, Martijn _______________________________________________ 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 )