Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [udig-dev] initial code check-in

Jody, I'm not sure whether I got your point. Althought we can work in github you like to move to LocationTech hosted git repository (and mirror this back to LocationTech group repository at github)?

Is this neccessary to be in Position to use build and hosting infrastructure and relang functionality from eclipse common build infrastructure as well?

Or is it about adding eclipse git as remote repository to our working copy and push master to upstream master, rebase luna branch and push it to upstream as well?

An other point for sure are committer access to all the other tools such as bugzilla, Gerrit, Hudson and so in. Make sense for move to LocationTech but currently have no idea how the workflow would look like if committers working with github repository

Maybe we should chat about it with Andrew.

Am 14.10.2014 20:18 schrieb "Jody Garnett" <jody.garnett@xxxxxxxxx>:
Follow up to conversation with Frank at foss4g.

A while back (April 2013) we got tentative permission to "check in" our initial code contribution (subject to the GlobalMercator GPL file being removed).

Now that LocationTech is up and running, and lets us work from GitHub, I would like to go ahead and move the repository over.

Notes:
- check everyone has access to github.com/locationtech
- locally you will change your upstream repository settings
- we will create repo based on the current state of master (using GeoTools 11.2)
- can create a new branch for the luna upgrade (since that is being rebased for GeoTools 11.2)

--
Jody Garnett

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

Back to the top