Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [geogig-dev] GeoGig release progress
Hmm... so I didn't realize that someone had removed the issues from the new github repo. I was using it to track the changes required by the IP review. Does anyone know if those can be retrieved? My IP pull request is now full of dead links.

I've been neglecting GeoGig for the last month or so. I hope to catch up next week.


On 5 March 2015 at 12:11, Jody Garnett <jgarnett@xxxxxxxxxxxxxxxx> wrote:
It is private to the project, but as a committer you should be able to login and see it. Creating a new IP ticket (when you want to update a dependency) is one of the things you can do using that eclipse portal.

I think gabriel focused on migrating the source code, and not the open issues. Gabriel could ask for that to be ported over - what do you think Gabriel?

On Thu, Mar 5, 2015 at 11:45 AM, Scott <sctevl@xxxxxxxxx> wrote:


On Thu, Mar 5, 2015 at 2:04 PM, Jody Garnett <jgarnett@xxxxxxxxxxxxxxxx> wrote:
Right now those issues are in "IP Zilla" (yes that is as scary as it sounds a bugzilla full of IP tickets). I think for each rejection Tyler has been handling it (removing jgridshift as a dependency) or taking it to the appropriate community for discussion (vecmath).

Is that public? Can we track progress?
 

Thanks for pointing me in the right direction. It's empty though. Looks like the issues haven't been migrated over yet.
 

Andrew was checking if LocationTech could set up a Jira (if we would like to use that rather than their bug tracker). The guiding principle here (as I understand it) is they want a backup of the source code and issues in case a service goes dark ... normally I would laugh at this but codehaus is shutting down taking all of my geotools issues with it :(

So if geogig wants to keep using github issue tracker we will need to ask, and possibly assist with automated backup.

My feeling is that the issues were taken down too soon on GitHub. No one can see what issues are outstanding with the code now or the history and disposition of the old issues. I'm not trying to shoot the messenger though. I'm just disappointed. 

Cheers,

 Scott
 

_______________________________________________
geogig-dev mailing list
geogig-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geogig-dev



--

_______________________________________________
geogig-dev mailing list
geogig-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geogig-dev



--

Tyler Battle

Software Engineer| Boundless

tbattle@xxxxxxxxxxxxxxxx

Victoria, BC, Canada


Back to the top