[mapserver-dev] RFC84 call for vote: migrate from svn/trac to
Lime, Steve D (DNR)
Steve.Lime at state.mn.us
Mon Apr 2 13:07:20 EDT 2012
Note I'm +1 on the move. I'd just like to know how to handle the couple of inconveniences in a standard way.
From: mapserver-dev-bounces at lists.osgeo.org [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of Lime, Steve D (DNR)
Sent: Monday, April 02, 2012 11:45 AM
To: thomas bonfort; MapServer Dev Mailing List
Subject: RE: [mapserver-dev] RFC84 call for vote: migrate from svn/trac to git/github
Regarding the inconveniences:
- How to handle private security tickets? In all likelihood we will need this capability. Fall back to OSGeo trac instance until a public ticket can be created?
- Image attachments. Can/should we specify a standard approach, a mapserver-specific collection point?
On the githup side how does my github user (sdlime) get associated with "Steve Lime" in the repository?
From: mapserver-dev-bounces at lists.osgeo.org [mailto:mapserver-dev-bounces at lists.osgeo.org] On Behalf Of thomas bonfort
Sent: Monday, April 02, 2012 9:28 AM
To: MapServer Dev Mailing List
Subject: [mapserver-dev] RFC84 call for vote: migrate from svn/trac to git/github
I have updated the RFC with the discussion related to ticket history (which can be nearly seamlessly imported), and removed the option of continuing using the current trac instance.
The target result can be found here: https://github.com/mapserver (still missing the msautotest and tinyows repos, and with a temporary ms-import one)
Given that the discussion around this RFC has happened and that most of the reluctances have been sorted out, I would like to call for a vote on this. In case of success, trac and svn would need to be freezed, and we could be up and running on github by the end of the week.
I'll start with my +1
mapserver-dev mailing list
mapserver-dev at lists.osgeo.org
More information about the mapserver-dev