Re: [Zope-dev] How to signal that projects have moved to github

2013-01-11 Thread Marius Gedminas
On Thu, Jan 10, 2013 at 05:37:09PM -0500, Tres Seaver wrote: On 01/10/2013 03:16 PM, Marius Gedminas wrote: On Thu, Jan 10, 2013 at 09:15:21AM -0500, Jim Fulton wrote: An argument against cleaning out trunk will break CI tools. This is also an argument *for* cleaning out trunk. :)

Re: [Zope-dev] How to signal that projects have moved to github

2013-01-11 Thread Chris Withers
On 10/01/2013 20:48, Jim Fulton wrote: It isn't just CI: people may have projects running from SVN checkouts, which we break without warning (the Plone devs have been notorious for causing such breakage for years). I still think breakage is better. If they're using trunk, without pinning a

[Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Jim Fulton
I'd like us to agree on how we're going to indicate in SVN that projects have been moved to github. Here's an opening bid: - Replace contents of trunk with a single file MOVED_TO_GITHUB containing the URL if the project page in github - Copy above file to root of project. - Make project read

Re: [Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Brian Sutherland
On Thu, Jan 10, 2013 at 09:15:21AM -0500, Jim Fulton wrote: I'd like us to agree on how we're going to indicate in SVN that projects have been moved to github. Here's an opening bid: - Replace contents of trunk with a single file MOVED_TO_GITHUB containing the URL if the project page in

Re: [Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Patrick Gerken
I am in favor of removing the trunks. People who do not want to switch to git can still get the trunk by pinning to a specific revision. I run a CI tool and it is broken already because apparently a trunk has been deleted already. Thats not a bug, thats why I run the CI Tool. Would be stupid if I

Re: [Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 09:15 AM, Jim Fulton wrote: I'd like us to agree on how we're going to indicate in SVN that projects have been moved to github. Here's an opening bid: - Replace contents of trunk with a single file MOVED_TO_GITHUB containing

Re: [Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 10:42 AM, Patrick Gerken wrote: I am in favor of removing the trunks. People who do not want to switch to git can still get the trunk by pinning to a specific revision. I run a CI tool and it is broken already because apparently a

Re: [Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Marius Gedminas
On Thu, Jan 10, 2013 at 09:15:21AM -0500, Jim Fulton wrote: I'd like us to agree on how we're going to indicate in SVN that projects have been moved to github. Here's an opening bid: - Replace contents of trunk with a single file MOVED_TO_GITHUB containing the URL if the project page in

Re: [Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Jim Fulton
On Thu, Jan 10, 2013 at 12:02 PM, Tres Seaver tsea...@palladion.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 10:42 AM, Patrick Gerken wrote: I am in favor of removing the trunks. People who do not want to switch to git can still get the trunk by pinning to a

Re: [Zope-dev] How to signal that projects have moved to github

2013-01-10 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2013 03:16 PM, Marius Gedminas wrote: On Thu, Jan 10, 2013 at 09:15:21AM -0500, Jim Fulton wrote: An argument against cleaning out trunk will break CI tools. This is also an argument *for* cleaning out trunk. :) Thoughts? +1