Re: [Zope-dev] Zope 4 release management

2012-06-12 Thread Jan-Carel Brand
Hi Patrick On Mon, 2012-06-11 at 18:36 +0200, Patrick Gerken wrote: snip Since I most often look for the history of something in SVN, I decided to finally make a git mirror for myself to quickly find the history of anything I might ever want. Since its for history only, I just imported the

Re: [Zope-dev] Zope 4 release management

2012-06-12 Thread Patrick Gerken
On Tue, Jun 12, 2012 at 2:50 PM, Jan-Carel Brand li...@opkode.com wrote: Do you also sync the git repo with new changes from the svn repo? Yes, but unfortunately 1. It takes ages 2. I have to do it on my laptop because none of my servers has enough inodes for that task. I do it once a day at

Re: [Zope-dev] Zope 4 release management

2012-06-11 Thread Patrick Gerken
Hi, The ZF notes from May mentioned a VCS discussion. Is this the the latest thread or did I miss one more current for some reason? On Wed, Feb 1, 2012 at 3:40 PM, Alexandre Garel alex.ga...@tarentis.com wrote: Le 01/02/2012 14:21, Lennart Regebro a écrit : With dvcs everyone got full history

Re: [Zope-dev] Zope 4 release management

2012-02-06 Thread Martijn Faassen
On 11/17/2011 07:01 PM, Martin Aspeli wrote: I would actually argue that Zope4 have no real release cycle at all: instead, the individual pieces which make up Zope should have their own cycles, with perhaps a ZTK-like tracking set that Plone and others use as platform targets. -1 - we'll need

Re: [Zope-dev] Zope 4 release management

2012-02-06 Thread Hanno Schlichting
On Mon, Feb 6, 2012 at 4:41 PM, Martijn Faassen faas...@startifact.com wrote: I would actually argue that Zope4 have no real release cycle at all: instead, the individual pieces which make up Zope should have their own cycles, with perhaps a ZTK-like tracking set that Plone and others use as

Re: [Zope-dev] Zope 4 release management

2012-02-04 Thread Chris McDonough
On Thu, 2012-02-02 at 08:46 +0100, Jens Vagelpohl wrote: Hi Chris, For what it's worth, in the Pylons Project, we decided to continue requiring the signing of a contributor's agreement (more or less the same contributor agreement as Zope requires). But instead of signing via paper, we

Re: [Zope-dev] Zope 4 release management

2012-02-02 Thread Lennart Regebro
On Wed, Feb 1, 2012 at 14:29, Alex Clark acl...@aclark.net wrote: On 2/1/12 8:21 AM, Lennart Regebro wrote: Should you then decide that github is the place  to host it, well, then git is the software to use. Actually, they introduced improved Subversion client support late last year: -

Re: [Zope-dev] Zope 4 release management

2012-02-02 Thread Lennart Regebro
On Wed, Feb 1, 2012 at 15:40, Alexandre Garel alex.ga...@tarentis.com wrote: I'm a bit amazed by this argumentation. I think one important thing is that subversion is centralized while dvcs are not. And I think it's very unimportant. With dvcs everyone got full history of zope libs. I

Re: [Zope-dev] Zope 4 release management

2012-02-01 Thread Jens Vagelpohl
On Feb 1, 2012, at 00:05 , Alex Clark wrote: Bottom line: Zope stands to benefit greatly if the current active developers keep an open mind about how/where/when development of Zope software should occur. There are plenty of people that still think Zope software is cool, and plenty of

Re: [Zope-dev] Zope 4 release management

2012-02-01 Thread Alex Clark
On 2/1/12 6:08 AM, Jens Vagelpohl wrote: On Feb 1, 2012, at 00:05 , Alex Clark wrote: Bottom line: Zope stands to benefit greatly if the current active developers keep an open mind about how/where/when development of Zope software should occur. There are plenty of people that still think

Re: [Zope-dev] Zope 4 release management

2012-02-01 Thread Lennart Regebro
On Wed, Feb 1, 2012 at 13:03, Alex Clark acl...@aclark.net wrote: - what RCS software to use - where to host it It may be easier if we disentangled them. Traditionally it was easier, but now-a-days with github and bitbucket they are harder to disentangle. It is entangled, but it is

Re: [Zope-dev] Zope 4 release management

2012-02-01 Thread Alex Clark
On 2/1/12 8:21 AM, Lennart Regebro wrote: On Wed, Feb 1, 2012 at 13:03, Alex Clarkacl...@aclark.net wrote: - what RCS software to use - where to host it It may be easier if we disentangled them. Traditionally it was easier, but now-a-days with github and bitbucket they are harder to

Re: [Zope-dev] Zope 4 release management

2012-02-01 Thread Wichert Akkerman
On 02/01/2012 02:29 PM, Alex Clark wrote: Actually, they introduced improved Subversion client support late last year: - https://github.com/blog/966-improved-subversion-client-support Unfortunately it is too unstable to be usable. Wichert. ___

Re: [Zope-dev] Zope 4 release management

2012-02-01 Thread Jonathan Ballet
On Wed, Feb 01, 2012 at 02:21:32PM +0100, Lennart Regebro wrote: What we would like to do, of course, is to have a self-hosted github. :-) (And that exists. Buuut... it costs $250 per commiter and year, so that's not an option, obviously.) Just to be sure I keep the fire on: what about

Re: [Zope-dev] Zope 4 release management

2012-02-01 Thread Alexandre Garel
Le 01/02/2012 14:21, Lennart Regebro a écrit : I do think the big issue is where to host it. Yes, fine, people have opinions on git vs svn vs hg, etc. But that boils down to 25% technical arguments, 25% what you are used to 25% what everyone else uses and then 30% religion to make sure the

Re: [Zope-dev] Zope 4 release management

2012-02-01 Thread Charlie Clark
Am 01.02.2012, 15:40 Uhr, schrieb Alexandre Garel alex.ga...@tarentis.com: All I see here is usability not religion Which is pretty much what Jens said originally. To me, much of the argument seems to be trying to solve a different problem: getting more people involved in contributing to

Re: [Zope-dev] Zope 4 release management

2012-02-01 Thread Laurence Rowe
On 1 February 2012 14:35, Jonathan Ballet j...@multani.info wrote: On Wed, Feb 01, 2012 at 02:21:32PM +0100, Lennart Regebro wrote: What we would like to do, of course, is to have a self-hosted github. :-)  (And that exists. Buuut... it costs $250 per commiter and year, so that's not an

Re: [Zope-dev] Zope 4 release management

2012-02-01 Thread Jens Vagelpohl
On Feb 1, 2012, at 15:53 , Charlie Clark wrote: Currently the hurdle to getting involved is signing and sending the committer agreement. A hurdle which I think is worth keeping. For any code released under the Zope Foundation umbrella that hurdle cannot be removed, anyway. To be frank, I

Re: [Zope-dev] Zope 4 release management

2012-02-01 Thread Chris McDonough
On Wed, 2012-02-01 at 16:29 +0100, Jens Vagelpohl wrote: On Feb 1, 2012, at 15:53 , Charlie Clark wrote: Currently the hurdle to getting involved is signing and sending the committer agreement. A hurdle which I think is worth keeping. For any code released under the Zope Foundation

Re: [Zope-dev] Zope 4 release management

2012-02-01 Thread Jens Vagelpohl
Hi Chris, For what it's worth, in the Pylons Project, we decided to continue requiring the signing of a contributor's agreement (more or less the same contributor agreement as Zope requires). But instead of signing via paper, we ask that folks sign the contributor agreement by adding their

Re: [Zope-dev] Zope 4 release management

2012-01-31 Thread Alex Clark
Hi, Late chime-in below: On 11/17/11 2:45 PM, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/17/2011 01:01 PM, Martin Aspeli wrote: On 17 November 2011 16:32, Tres Seavertsea...@palladion.com wrote: * Zope 4 will not have a release cycle independent of Plone. Zope

[Zope-dev] Zope 4 release management

2011-11-17 Thread Laurence Rowe
Along with David Glick, I would like to volunteer for the Zope 4 release management role, where I would take responsibility for producing the initial release of Zope 4 and David would then take over for the maintenance releases. In doing so, I thought it would be helpful to set out our

Re: [Zope-dev] Zope 4 release management

2011-11-17 Thread Martin Aspeli
Hi, On 17 November 2011 12:25, Laurence Rowe l...@lrowe.co.uk wrote: Along with David Glick, I would like to volunteer for the Zope 4 release management role, where I would take responsibility for producing the initial release of Zope 4 and David would then take over for the maintenance

Re: [Zope-dev] Zope 4 release management

2011-11-17 Thread Jim Fulton
On Thu, Nov 17, 2011 at 7:25 AM, Laurence Rowe l...@lrowe.co.uk wrote: ... (Interesting roadmap snipped) This process will  necessitate a lot of merging, so I want to propose that we move to Git for development (something we found very helpful at our recent San Francisco Zope 4 sprint.) I

Re: [Zope-dev] Zope 4 release management

2011-11-17 Thread Martin Aspeli
On 17 November 2011 15:50, Jim Fulton j...@zope.com wrote: On Thu, Nov 17, 2011 at 7:25 AM, Laurence Rowe l...@lrowe.co.uk wrote: ... (Interesting roadmap snipped) This process will  necessitate a lot of merging, so I want to propose that we move to Git for development (something we found

Re: [Zope-dev] Zope 4 release management

2011-11-17 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/17/2011 07:25 AM, Laurence Rowe wrote: Along with David Glick, I would like to volunteer for the Zope 4 release management role, where I would take responsibility for producing the initial release of Zope 4 and David would then take over

Re: [Zope-dev] Zope 4 release management

2011-11-17 Thread Chris Withers
On 17/11/2011 16:32, Tres Seaver wrote: Note that this question is *not* suitable for loudest voice on zope-dev wins ressolution. The software belongs to the Zope Foundation, which will make any such decision. Small point: the software is open source and anyone who wants can maintain it

Re: [Zope-dev] Zope 4 release management

2011-11-17 Thread Martin Aspeli
On 17 November 2011 16:32, Tres Seaver tsea...@palladion.com wrote: * Zope 4 will not seek to innovate in itself but encourage innovation in software components shared with the wider Python web community. I smell something funny in here:  if we aren't innovating, why are we making the

Re: [Zope-dev] Zope 4 release management

2011-11-17 Thread Laurence Rowe
On 17 November 2011 16:32, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/17/2011 07:25 AM, Laurence Rowe wrote: Along with David Glick, I would like to volunteer for the Zope 4 release management role, where I would take responsibility for

Re: [Zope-dev] Zope 4 release management

2011-11-17 Thread Laurence Rowe
On 17 November 2011 19:45, Tres Seaver tsea...@palladion.com wrote: Again, this is a choice to be made by the foundation:  any polling will be done by the members of the foundation (this might be the biggest non-election item on the agenda for the next annual meeting). When is the next annual

Re: [Zope-dev] Zope 4 release management

2011-11-17 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/17/2011 03:14 PM, Laurence Rowe wrote: On 17 November 2011 19:45, Tres Seaver tsea...@palladion.com wrote: Again, this is a choice to be made by the foundation: any polling will be done by the members of the foundation (this might be the

Re: [Zope-dev] Zope 4 release management

2011-11-17 Thread Laurence Rowe
On 17 November 2011 20:20, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/17/2011 03:14 PM, Laurence Rowe wrote: On 17 November 2011 19:45, Tres Seaver tsea...@palladion.com wrote: Again, this is a choice to be made by the foundation:  any