You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@guacamole.apache.org by Mike Jumper <mj...@apache.org> on 2019/01/10 19:58:27 UTC
[DISCUSS] Migration of git repositories to gitbox (Was: Re: [NOTICE]
Mandatory migration of git repositories to gitbox.apache.org)
Greetings all,
All projects under the ASF using git are eventually being migrated to
gitbox. Now that 1.0.0 is out of the way, there seems little reason/benefit
to put this off. It will happen automatically on February 7th, but we can
opt in to doing this sooner.
Thoughts on opting in to an earlier migration? Seems way better to me than
being "mass migrated without warning" come 2019-02-07...
If there's general consensus, I'll create a ticket with Infra pointing at
this thread and things will move forward.
See details below.
Thanks,
- Mike
On Thu, Jan 3, 2019 at 5:19 AM Apache Infrastructure Team <
infrastructure@apache.org> wrote:
> Hello, guacamole folks.
> As stated earlier in 2018, all git repositories must be migrated from
> the git-wip-us.apache.org URL to gitbox.apache.org, as the old service
> is being decommissioned. Your project is receiving this email because
> you still have repositories on git-wip-us that needs to be migrated.
>
> The following repositories on git-wip-us belong to your project:
> - guacamole-manual.git
> - guacamole-website.git
> - guacamole-server.git
> - guacamole-client.git
>
>
> We are now entering the mandated (coordinated) move stage of the roadmap,
> and you are asked to please coordinate migration with the Apache
> Infrastructure Team before February 7th. All repositories not migrated
> on February 7th will be mass migrated without warning, and we'd appreciate
> it if we could work together to avoid a big mess that day :-).
>
> Moving to gitbox means you will get full write access on GitHub as well,
> and be able to close/merge pull requests and much more.
>
> To have your repositories moved, please follow these steps:
>
> - Ensure consensus on the move (a link to a lists.apache.org thread will
> suffice for us as evidence).
> - Create a JIRA ticket at https://issues.apache.org/jira/browse/INFRA
>
> Your migration should only take a few minutes. If you wish to migrate
> at a specific time of day or date, please do let us know in the ticket.
>
> As always, we appreciate your understanding and patience as we move
> things around and work to provide better services and features for
> the Apache Family.
>
> Should you wish to contact us with feedback or questions, please do so
> at: users@infra.apache.org.
>
>
> With regards,
> Apache Infrastructure
>
>
Re: [DISCUSS] Migration of git repositories to gitbox (Was: Re:
[NOTICE] Mandatory migration of git repositories to gitbox.apache.org)
Posted by carl harris <ce...@gmail.com>.
I also vote for going ahead sooner... always better to control the timeline, and probably best not to get caught up in the mass migration.
carl
> On Jan 10, 2019, at 3:36 PM, Nick Couchman <vn...@apache.org> wrote:
>
> On Thu, Jan 10, 2019 at 14:59 Mike Jumper <mj...@apache.org> wrote:
>
>> Greetings all,
>>
>> All projects under the ASF using git are eventually being migrated to
>> gitbox. Now that 1.0.0 is out of the way, there seems little reason/benefit
>> to put this off. It will happen automatically on February 7th, but we can
>> opt in to doing this sooner.
>>
>> Thoughts on opting in to an earlier migration? Seems way better to me than
>> being "mass migrated without warning" come 2019-02-07...
>>
>>
> I vote for going ahead with it sooner - go ahead and open a ticket with
> infra and see if maybe they can get it done this weekend? No reason I can
> see to wait, and I think it'll only impact committers, correct? Should be
> transparent on the GitHub side of things?
>
> -Nick
Re: [DISCUSS] Migration of git repositories to gitbox (Was: Re:
[NOTICE] Mandatory migration of git repositories to gitbox.apache.org)
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
it's on the way for the four repositories. I should be done today.
Regards
JB
On 12/01/2019 21:11, Nick Couchman wrote:
> On Fri, Jan 11, 2019 at 1:44 AM Mike Jumper <mj...@apache.org> wrote:
>
>> On Thu, Jan 10, 2019, 22:29 Jean-Baptiste Onofré <jb@nanthrax.net wrote:
>>
>>> Hi,
>>>
>>> No problem to do it now. It's very fast (let's 5 minutes) and smooth ;)
>>>
>>> Do you want me to create a Jira for INFRA ?
>>>
>>
>> Sure! Thanks, JB.
>>
>> - Mike
>>
>
> Thanks for doing this, JB. Any word on the timeline for it (maybe it's
> already done)?
>
> -Nick
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [DISCUSS] Migration of git repositories to gitbox (Was: Re:
[NOTICE] Mandatory migration of git repositories to gitbox.apache.org)
Posted by Mike Jumper <mj...@apache.org>.
So far, so good. We can merge with the merge button! Beware that GitHub now
apparently provides two fields for the merge commit message. This threw me
at first (isn't there only one message for a commit?) but it's really all
for the same message. The first field is the first line, while the second,
multi-line field is for an optional extended description to be included
after a blank line in the same message.
There seems to be some issues with the way emails, etc. work:
1) Once merged, the email from GitBox alerting to the merge
introduces/complains about GitHub behavior twice. Based on how it's worded,
it looks like this was two attempts to say the same thing, only one of
which was meant to be kept:
"[absolute ton of blank lines]
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
[the diff]"
2) GitBox automatically comments on the associated JIRA issue with an
incorrect / partly useless comment saying that the committer that merged
the PR commented on the PR:
"mike-jumper commented on pull request #351: GUACAMOLE-683: Add OpenID
support in Docker Build Scripts
URL: https://github.com/apache/guacamole-client/pull/351
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org"
(see
https://issues.apache.org/jira/browse/GUACAMOLE-683?focusedCommentId=16741527&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16741527
)
It'd be nice if GitHub integration for JIRA were installed rather than
having a bot comment on issues. The GitHub integration maintains a nice,
unobtrusive list of relevant commits and the status of associated pull
requests. I'm not sure why it's necessary to have an in-house bot comment
and create links when a polished integration for JIRA already exists.
3) No emails containing the actual commits are sent out to commits@. There
is an email regarding the pull request closure that goes to commits@ and
others for the various commits, but those only the diff statistics and
commit message, not the diff/commit itself. There is one message that does
contain the entire diff (the one mentioned in #1 above), but it goes to dev@
and contains the entire diff. Whatever happened to the old functionality
where there was one email per commit sent to commits@? Doesn't git provide
its own commit to email mapping out-of-the-box?
I'd think that there would be email-formatted diffs for the new commits
sent to commits@, and a simple message (no diff) noting the fact that PR
was merged sent to dev@.
- Mike
On Sun, Jan 13, 2019 at 1:22 AM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> Done, the repositories are now on gitbox.
>
> You just have to update the git remote.
>
> Regards
> JB
>
> On 12/01/2019 21:11, Nick Couchman wrote:
> > On Fri, Jan 11, 2019 at 1:44 AM Mike Jumper <mj...@apache.org> wrote:
> >
> >> On Thu, Jan 10, 2019, 22:29 Jean-Baptiste Onofré <jb@nanthrax.net
> wrote:
> >>
> >>> Hi,
> >>>
> >>> No problem to do it now. It's very fast (let's 5 minutes) and smooth ;)
> >>>
> >>> Do you want me to create a Jira for INFRA ?
> >>>
> >>
> >> Sure! Thanks, JB.
> >>
> >> - Mike
> >>
> >
> > Thanks for doing this, JB. Any word on the timeline for it (maybe it's
> > already done)?
> >
> > -Nick
> >
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: [DISCUSS] Migration of git repositories to gitbox (Was: Re:
[NOTICE] Mandatory migration of git repositories to gitbox.apache.org)
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Done, the repositories are now on gitbox.
You just have to update the git remote.
Regards
JB
On 12/01/2019 21:11, Nick Couchman wrote:
> On Fri, Jan 11, 2019 at 1:44 AM Mike Jumper <mj...@apache.org> wrote:
>
>> On Thu, Jan 10, 2019, 22:29 Jean-Baptiste Onofré <jb@nanthrax.net wrote:
>>
>>> Hi,
>>>
>>> No problem to do it now. It's very fast (let's 5 minutes) and smooth ;)
>>>
>>> Do you want me to create a Jira for INFRA ?
>>>
>>
>> Sure! Thanks, JB.
>>
>> - Mike
>>
>
> Thanks for doing this, JB. Any word on the timeline for it (maybe it's
> already done)?
>
> -Nick
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [DISCUSS] Migration of git repositories to gitbox (Was: Re:
[NOTICE] Mandatory migration of git repositories to gitbox.apache.org)
Posted by Nick Couchman <vn...@apache.org>.
On Fri, Jan 11, 2019 at 1:44 AM Mike Jumper <mj...@apache.org> wrote:
> On Thu, Jan 10, 2019, 22:29 Jean-Baptiste Onofré <jb@nanthrax.net wrote:
>
> > Hi,
> >
> > No problem to do it now. It's very fast (let's 5 minutes) and smooth ;)
> >
> > Do you want me to create a Jira for INFRA ?
> >
>
> Sure! Thanks, JB.
>
> - Mike
>
Thanks for doing this, JB. Any word on the timeline for it (maybe it's
already done)?
-Nick
Re: [DISCUSS] Migration of git repositories to gitbox (Was: Re:
[NOTICE] Mandatory migration of git repositories to gitbox.apache.org)
Posted by Mike Jumper <mj...@apache.org>.
On Thu, Jan 10, 2019, 22:29 Jean-Baptiste Onofré <jb@nanthrax.net wrote:
> Hi,
>
> No problem to do it now. It's very fast (let's 5 minutes) and smooth ;)
>
> Do you want me to create a Jira for INFRA ?
>
Sure! Thanks, JB.
- Mike
Re: [DISCUSS] Migration of git repositories to gitbox (Was: Re:
[NOTICE] Mandatory migration of git repositories to gitbox.apache.org)
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
No problem to do it now. It's very fast (let's 5 minutes) and smooth ;)
Do you want me to create a Jira for INFRA ?
Regards
JB
On 10/01/2019 21:47, Nick Couchman wrote:
> On Thu, Jan 10, 2019 at 15:41 Mike Jumper <mj...@apache.org> wrote:
>
>> On Thu, Jan 10, 2019, 12:36 Nick Couchman <vnick@apache.org wrote:
>>
>>> On Thu, Jan 10, 2019 at 14:59 Mike Jumper <mj...@apache.org> wrote:
>>>
>>>> Greetings all,
>>>>
>>>> All projects under the ASF using git are eventually being migrated to
>>>> gitbox. Now that 1.0.0 is out of the way, there seems little
>>> reason/benefit
>>>> to put this off. It will happen automatically on February 7th, but we
>> can
>>>> opt in to doing this sooner.
>>>>
>>>> Thoughts on opting in to an earlier migration? Seems way better to me
>>> than
>>>> being "mass migrated without warning" come 2019-02-07...
>>>>
>>>>
>>> I vote for going ahead with it sooner - go ahead and open a ticket with
>>> infra and see if maybe they can get it done this weekend? No reason I
>> can
>>> see to wait, and I think it'll only impact committers, correct? Should
>> be
>>> transparent on the GitHub side of things?
>>
>>
>> Right. I believe the only effect is going to be in the way pull requests
>> are handled on the merge side. For contributors opening pull requests,
>> users cloning the repository, etc., nothing changes.
>>
>
> Then this seems like the perfect time to do it before we start creating
> branches and such to prep for the next release :-)!
>
> -Nick
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [DISCUSS] Migration of git repositories to gitbox (Was: Re:
[NOTICE] Mandatory migration of git repositories to gitbox.apache.org)
Posted by Nick Couchman <vn...@apache.org>.
On Thu, Jan 10, 2019 at 15:41 Mike Jumper <mj...@apache.org> wrote:
> On Thu, Jan 10, 2019, 12:36 Nick Couchman <vnick@apache.org wrote:
>
> > On Thu, Jan 10, 2019 at 14:59 Mike Jumper <mj...@apache.org> wrote:
> >
> > > Greetings all,
> > >
> > > All projects under the ASF using git are eventually being migrated to
> > > gitbox. Now that 1.0.0 is out of the way, there seems little
> > reason/benefit
> > > to put this off. It will happen automatically on February 7th, but we
> can
> > > opt in to doing this sooner.
> > >
> > > Thoughts on opting in to an earlier migration? Seems way better to me
> > than
> > > being "mass migrated without warning" come 2019-02-07...
> > >
> > >
> > I vote for going ahead with it sooner - go ahead and open a ticket with
> > infra and see if maybe they can get it done this weekend? No reason I
> can
> > see to wait, and I think it'll only impact committers, correct? Should
> be
> > transparent on the GitHub side of things?
>
>
> Right. I believe the only effect is going to be in the way pull requests
> are handled on the merge side. For contributors opening pull requests,
> users cloning the repository, etc., nothing changes.
>
Then this seems like the perfect time to do it before we start creating
branches and such to prep for the next release :-)!
-Nick
Re: [DISCUSS] Migration of git repositories to gitbox (Was: Re:
[NOTICE] Mandatory migration of git repositories to gitbox.apache.org)
Posted by Mike Jumper <mj...@apache.org>.
On Thu, Jan 10, 2019, 12:36 Nick Couchman <vnick@apache.org wrote:
> On Thu, Jan 10, 2019 at 14:59 Mike Jumper <mj...@apache.org> wrote:
>
> > Greetings all,
> >
> > All projects under the ASF using git are eventually being migrated to
> > gitbox. Now that 1.0.0 is out of the way, there seems little
> reason/benefit
> > to put this off. It will happen automatically on February 7th, but we can
> > opt in to doing this sooner.
> >
> > Thoughts on opting in to an earlier migration? Seems way better to me
> than
> > being "mass migrated without warning" come 2019-02-07...
> >
> >
> I vote for going ahead with it sooner - go ahead and open a ticket with
> infra and see if maybe they can get it done this weekend? No reason I can
> see to wait, and I think it'll only impact committers, correct? Should be
> transparent on the GitHub side of things?
Right. I believe the only effect is going to be in the way pull requests
are handled on the merge side. For contributors opening pull requests,
users cloning the repository, etc., nothing changes.
- Mike
Re: [DISCUSS] Migration of git repositories to gitbox (Was: Re:
[NOTICE] Mandatory migration of git repositories to gitbox.apache.org)
Posted by Nick Couchman <vn...@apache.org>.
On Thu, Jan 10, 2019 at 14:59 Mike Jumper <mj...@apache.org> wrote:
> Greetings all,
>
> All projects under the ASF using git are eventually being migrated to
> gitbox. Now that 1.0.0 is out of the way, there seems little reason/benefit
> to put this off. It will happen automatically on February 7th, but we can
> opt in to doing this sooner.
>
> Thoughts on opting in to an earlier migration? Seems way better to me than
> being "mass migrated without warning" come 2019-02-07...
>
>
I vote for going ahead with it sooner - go ahead and open a ticket with
infra and see if maybe they can get it done this weekend? No reason I can
see to wait, and I think it'll only impact committers, correct? Should be
transparent on the GitHub side of things?
-Nick