Re: How to signal that projects have moved to github

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 continue
to test a trunk not in use.

Best regards,

   Patrick


On Thu, Jan 10, 2013 at 3:15 PM, Jim Fulton <[email protected]> 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 github
>
> - Copy above file to root of project.
>
> - Make project read only
>
> An argument against cleaning out trunk will break
> CI tools.  This is also an argument *for* cleaning
> out trunk. :)
>
> Thoughts?
>
> There are a lot of other details of the migration that need
> to be worked out, like how folks should request migration and
> automating the conversion further.
>
> Jim
>
> --
> Jim Fulton
> http://www.linkedin.com/in/jimfulton
> Jerky is better than bacon! http://zo.pe/Kqm
> _______________________________________________
> Zope-Dev maillist  -  [email protected]
> https://mail.zope.org/mailman/listinfo/zope-dev
> **  No cross posts or HTML encoding!  **
> (Related lists -
>  https://mail.zope.org/mailman/listinfo/zope-announce
>  https://mail.zope.org/mailman/listinfo/zope )
>

_______________________________________________
Zope-Dev maillist  -  [email protected]
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )