[mapserver-dev] github migration complete

[Stephen Woodbridge]

Steve,

I don't know what it takes, but can we lock trac and svn so they are 
read only?

I think an announce is a good idea.

-Steve W

On 4/5/2012 12:08 PM, Lime, Steve D (DNR) wrote:
> I think we need to get some communications out to mapserver-users
> letting them know about the change and that they should avoid
> creating or updating trac tickets for days. If we're ready to send
> them to github then that should be mentioned to. There were several
> tickets updated that I saw emails on.
>
> Perhaps we could update the http://trac.osgeo.org/mapserver/ wiki
> page to direct users appropriately?
>
> Steve
>
>
> -----Original Message----- From:
> mapserver-dev-bounces at lists.osgeo.org
> [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of thomas
> bonfort Sent: Tuesday, April 03, 2012 10:55 PM To: MapServer Dev
> Mailing List Subject: [mapserver-dev] github migration complete
>
> Hi devs,
>
> As you may have seen or been notified, the transition of the code to
> github is complete, and the tickets have been imported. All code
> committers should normally have been added, I'm still missing jeff's
> userid for the docs.
>
> - How can we set trac and svn to read-only? - I can assign open
> issues to the person they were assigned in trac, but have refrained
> from doing so until now to avoid notification email spamming. I will
> do this in a couple of days once the dust has settled, unless you
> specifically oppose to this in this thread. - There are 5 major
> repositories: mapserver, docs, msautotest, mapcache, and tinyows. The
> mapcache and tinyows subdirectories in mapserver will have to be
> removed. - The tinyows code has been reimported from a dump of the
> original svn, which means it now has history attached. - There are a
> couple of trac issues and svn commits that didn't make it into github
> (i.e. the ones that were created after I got the trac dump): - from
> steveW: tickets 4270-4273 - from steveL: ticket 4269 + commit - from
> paolo: italian doc commit r13314
>
> - There is a single issue tracker for all repositories
> https://github.com/mapserver/mapserver/issues . The syntx reference
> is here http://github.github.com/github-flavored-markdown/ . You can
> reference commits by their sha1 directly (e.g. "in commit abd234ef ,
> the behavior ...") for commits that belong to the mapserver/mapserver
> repository. For commits in the other repositories, the syntax is
> mapserver/repo at SHA1, you have a nice example in the last comments of
> this ticket https://github.com/mapserver/mapserver/issues/3906 .
>
> cheers, thomas _______________________________________________
> mapserver-dev mailing list mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
>
>
>
> _______________________________________________ mapserver-dev mailing
> list mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev