On 02/21/2017 05:23 PM, Clebert Suconic wrote:
I suggest you start with adding the current version there, you make
progress... later you cherry-pick the commits or rebase against the
new repo.
This makes a lot more sense to convert it to git then.
If I don't get any -1 in 2 days, I will assume lazy consensus and open
the JIRA on infra.
Do you have a plan on what you are going to request? There are actually
several SVN repos under the NMS project and if we are migrating the AMQP
one then I'd suggest that all be moved so you should ensure you capture
them all. There's also some logistics involved in the move such as
whether the current repos be left intact in a read-only state or removed
after the migration. You'll also need to ensure infra migrates the
configuration to svngit2jira for each to the new repos and also get the
github mirroring setup for each.
There are some other tasks after that you'd need to do around ensuring
that the repos get shifted from trunk as the root to a master branch.
So before you do anything I suggest you work up a plan.
On Tue, Feb 21, 2017 at 5:08 PM, Duane Pauls <[email protected]> wrote:
For the NMS AMQP rework, we've created a github repo as a starting point:
https://github.com/SolaceLabs/nms-amqp
It's rather empty at the moment, but the work has been kicked off in a fork:
https://github.com/cjwmorgan-sol-sys/nms-amqp/
There isn't much there yet, but migrating to a git repository should make
it a bit easier to migrate changes over to the Apache repo.
So for me it is a (non-binding) +1.
On Tue, Feb 21, 2017 at 4:51 PM, nigro_franz <[email protected]> wrote:
For me is a +1!
--
View this message in context: http://activemq.2283324.n4.
nabble.com/DISCUSS-Move-Apache-NMS-project-to-Git-tp4722085p4722285.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/
