Re: [Zope-dev] Version Numbering for Ported Packages

2013-03-14 Thread Stephan Richter
On Wednesday, March 13, 2013 12:03:44 PM Tres Seaver wrote: We only moved packages that are still checked by winbot and the pnes that we ported because we use them in our project. 250+ of them? OK, I retract my concern then, if you are actually using them. The rough split is like that:

Re: [Zope-dev] Version Numbering for Ported Packages

2013-03-13 Thread Stephan Richter
On Wednesday, March 13, 2013 11:31:10 AM Tres Seaver wrote: FWIW whenever I get a failure notification from Travis about a package that doesn't have a .travis.yml, I uncheck the Active checkbox in Github repo settings. Unless the project already passes all its tests when run manually from

Re: [Zope-dev] Version Numbering for Ported Packages

2013-03-13 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/13/2013 12:05 PM, Stephan Richter wrote: On Wednesday, March 13, 2013 11:31:10 AM Tres Seaver wrote: FWIW whenever I get a failure notification from Travis about a package that doesn't have a .travis.yml, I uncheck the Active checkbox in

Re: [Zope-dev] Version Numbering for Ported Packages

2013-03-12 Thread Marius Gedminas
On Tue, Mar 12, 2013 at 08:35:46AM -0400, Stephan Richter wrote: On Monday, March 11, 2013 10:09:51 PM Tres Seaver wrote: Also, is somebody running / reporting tests via Travis? Where are those results going? They should be running for all packages. I have turned off any notifications

Re: [Zope-dev] Version Numbering for Ported Packages

2013-03-12 Thread Stephan Richter
On Tuesday, March 12, 2013 04:41:23 PM Marius Gedminas wrote: Note: I think most packages pass fine under Travis, but some are failing for some obscure reasons. An overview would be good. I could add a Travis column to http://zope3.pov.lt/py3/, I suppose. The image URLs are trivial to

[Zope-dev] Version Numbering for Ported Packages

2013-03-11 Thread Stephan Richter
Hi everyone, Fred asked about the reasoning behind recent version numbers as we ported packages to Python 3. We decided that any package that depends on an alpha or unreleased package should itself be an alpha release. There are 2 packages that started the avalanche: * zope.security: Tres

Re: [Zope-dev] Version Numbering for Ported Packages

2013-03-11 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/11/2013 08:40 PM, Stephan Richter wrote: Fred asked about the reasoning behind recent version numbers as we ported packages to Python 3. We decided that any package that depends on an alpha or unreleased package should itself be an alpha