[postgis-devel] is PostGIS ready for git ?

[Paul Ramsey]

I think it’s highly likely that as soon as our source code is in git, our workflow will migrate over to github pull requests, not because we are evil people, but because it is convenient, and because the input flow of contributions from that source will go up. That means that the internal process will become shattered between the lists, and the PR discussions, and the trac tickets will start to become stale holding places, slightly resented because they just add work without really adding value anymore. IE: spending time git’i’fying the trac is probably a waste of time, since as soon as we’re git’ed on the source, we’ll want to start routing around trac. If we’re going to spend the time processing trac entries to match git, why not spend the time migrating them to github and be done w/ it?

P. 

On October 13, 2015 at 1:41:04 AM, Sandro Santilli (strk at keybit.net) wrote:

NOTE: things are moving on the trac/git integration, you can
follow it here: https://trac.osgeo.org/osgeo/ticket/720

If you want to join the tests, file a ticket on the sandbox
project and request to be added to the group:
https://trac.osgeo.org/gittest

--strk;

On Mon, Oct 12, 2015 at 03:36:57PM +0200, 'Sandro Santilli' wrote:
> On Mon, Oct 12, 2015 at 08:56:28AM -0400, Paragon Corporation wrote:
> > My main issue with git was losing trac, but if we can have trac and git I'd
> > be fine with that.
>  
> I'm talking with Martin Spott about taking a step forward about that,
> they are using trac with git here: https://trac.osgeo.org/martin/
> take a look.
>  
> If you want to join, we're in #telascience IRC channel on freenode.
>  
> I believe you've done trac database massaging in the past, get ready
> because your ninja skills will be needed to convert all "r1234"
> references to "changeset:deadbeef", to keep cross references in sync
> (see https://lists.osgeo.org/pipermail/discuss/2015-October/015106.html)
>  
> --strk;
>  
> > -----Original Message-----
> > From: Sandro Santilli [mailto:sandro.santilli at gmail.com] On Behalf Of Sandro
> > Santilli
> > Sent: Monday, October 12, 2015 5:42 AM
> > To: postgis-devel at lists.osgeo.org
> > Cc: Paragon Corporation <lr at pcorp.us>; Paul Ramsey
> > <pramsey at cleverelephant.ca>; Bborie Park <dustymugs at gmail.com>; Mark
> > Cave-Ayland <mark.cave-ayland at ilande.co.uk>
> > Subject: is PostGIS ready for git ?
> >  
> > Devs, how comfortable are you with git nowadays ?
> >  
> > Would moving the PostGIS code repository to git present any trouble for
> > current contributors ? Or would it be mostly welcome ?
> >  
> > My list of troubles for moving to git are:
> >  
> > 1. Current OSGeo TRAC installation does not yet include support
> > for git: https://trac.osgeo.org/osgeo/ticket/720
> >  
> > 2. We don't have a recipe yet to update our ChangeLog file in a
> > compatible way
> >  
> > Anything else ?
> >  
> > --strk;
_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-devel

-- 
http://postgis.net
http://cleverelephant.ca

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20151013/fba6ffc8/attachment.html>