Re: [Zope-dev] Subversion merge tracking

2008-11-14 Thread Benji York
Given the current level of consensus, I plan on precluding pre-1.5
Subversion clients from making commits some time after the middle of
May 2009.

I'll try add some form of warning for affected users in the next
month or so.  If I can't get it to work I still plan to go forward
with the deprecation.
-- 
Benji York
Senior Software Engineer
Zope Corporation
___
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] Subversion merge tracking

2008-11-13 Thread Benji York
I'd like for us to disallow pre-1.5 Subversion clients from making
commits starting one year from now (or sooner if there is consensus).

The recent hardware problems for svn.zope.org had the positive outcome
of precipitating an upgrade to Subversion 1.5 which has merge tracking.
One of the requirements to use merge tracking is that no pre-1.5 client
merge to the branch that you want to use with merge tracking.

That means that as of now, anyone can use merge tracking on their
projects as long as all merges are done with a mergeinfo-capable (1.5+)
client.

Until we ban commits from pre-1.5 clients (using a pre-commit hook),
anyone who wants to use merge tracking will have to be careful with the
clients they use (and watch out for rouge merges from other contributors
which can be fixed-up after the fact).

The Subversion book includes information about merge tracking:
http://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html
http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html

A description of the pre-1.5 client problem is at
http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.branchmerge.advanced.pre1.5clients
-- 
Benji York
Senior Software Engineer
Zope Corporation
___
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] Subversion merge tracking

2008-11-13 Thread Jens Vagelpohl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


On Nov 13, 2008, at 14:42 , Benji York wrote:

 I'd like for us to disallow pre-1.5 Subversion clients from making
 commits starting one year from now (or sooner if there is consensus).

+1

jens



-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkkcQx4ACgkQRAx5nvEhZLKugACfUMq7DHVTzRNdF61grqsIzFdd
xqoAnRe5LpwZfh5JoD08z5Sj/SrOh0Ep
=Zf2H
-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] Subversion merge tracking

2008-11-13 Thread Sidnei da Silva
On Thu, Nov 13, 2008 at 1:09 PM, Jens Vagelpohl [EMAIL PROTECTED] wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1


 On Nov 13, 2008, at 14:42 , Benji York wrote:

 I'd like for us to disallow pre-1.5 Subversion clients from making
 commits starting one year from now (or sooner if there is consensus).

 +1

I vote for sooner, if that makes things easier. I'm already using 1.5
and I'm on Windows, so I guess the Linux users out there shouldn't
have a problem getting an up-to-date package right? :)

-- 
Sidnei da Silva
Enfold Systems
http://enfoldsystems.com
Fax +1 832 201 8856
Office +1 713 942 2377 Ext 214
Skype zopedc
___
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] Subversion merge tracking

2008-11-13 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Benji York wrote:
 I'd like for us to disallow pre-1.5 Subversion clients from making
 commits starting one year from now (or sooner if there is consensus).
 
 The recent hardware problems for svn.zope.org had the positive outcome
 of precipitating an upgrade to Subversion 1.5 which has merge tracking.
 One of the requirements to use merge tracking is that no pre-1.5 client
 merge to the branch that you want to use with merge tracking.
 
 That means that as of now, anyone can use merge tracking on their
 projects as long as all merges are done with a mergeinfo-capable (1.5+)
 client.
 
 Until we ban commits from pre-1.5 clients (using a pre-commit hook),
 anyone who wants to use merge tracking will have to be careful with the
 clients they use (and watch out for rouge merges from other contributors
 which can be fixed-up after the fact).
 
 The Subversion book includes information about merge tracking:
 http://svnbook.red-bean.com/nightly/en/svn.branchmerge.basicmerging.html
 http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html
 
 A description of the pre-1.5 client problem is at
 http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.branchmerge.advanced.pre1.5clients

+0, I guess:  I would be more comfortable if we could measure the
incidence of pre-1.5 client usage over time, and maybe even identify the
committers who are using them, so that we can sent out a targeted
warning message before breaking their checkouts.


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

iD8DBQFJHFWo+gerLs4ltQ4RAlDWAJ4mhFz6683K5eLs3T061ejSCaiIQACghWmn
OQjtYqIrO3TXnn5SsrjhrL4=
=Bncy
-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] Subversion merge tracking

2008-11-13 Thread Andreas Jung

On 13.11.2008 14:42 Uhr, Benji York wrote:

I'd like for us to disallow pre-1.5 Subversion clients from making
commits starting one year from now (or sooner if there is consensus).


+1 - six months should be enough for the transition.

Andreas

begin:vcard
fn:Andreas Jung
n:Jung;Andreas
org:ZOPYX Ltd.  Co. KG
adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany
email;internet:[EMAIL PROTECTED]
title:CEO
tel;work:+49-7071-793376
tel;fax:+49-7071-7936840
tel;home:+49-7071-793257
x-mozilla-html:FALSE
url:www.zopyx.com
version:2.1
end:vcard

___
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] Subversion merge tracking

2008-11-13 Thread Sidnei da Silva
On Thu, Nov 13, 2008 at 2:28 PM, Tres Seaver [EMAIL PROTECTED] wrote:
 +0, I guess:  I would be more comfortable if we could measure the
 incidence of pre-1.5 client usage over time, and maybe even identify the
 committers who are using them, so that we can sent out a targeted
 warning message before breaking their checkouts.

Checkouts are not a problem, only checkins.

-- 
Sidnei da Silva
Enfold Systems
http://enfoldsystems.com
Fax +1 832 201 8856
Office +1 713 942 2377 Ext 214
Skype zopedc
___
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] Subversion merge tracking

2008-11-13 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Sidnei da Silva wrote:
 On Thu, Nov 13, 2008 at 2:28 PM, Tres Seaver [EMAIL PROTECTED] wrote:
 +0, I guess:  I would be more comfortable if we could measure the
 incidence of pre-1.5 client usage over time, and maybe even identify the
 committers who are using them, so that we can sent out a targeted
 warning message before breaking their checkouts.
 
 Checkouts are not a problem, only checkins.

I'm talking about users who have *existing* checkouts on a pre-1.5
machine.  If they are make a commits from there, during the deprecation
period, we should collect that information, so that we can notify them
before breaking their ability to make further commits.


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

iD8DBQFJHFoi+gerLs4ltQ4RAkWcAJ97an0p0FjwGG2SuMLjIxVNw0FMBwCgsgOM
cQvNBSRv2YPTIlVIBSyIihk=
=8+my
-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 )