Re: [DISCUSS] Migration of git repositories to gitbox (Was: Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org)
On Thu, Jan 10, 2019, 22:29 Jean-Baptiste Onofré 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)
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 wrote: > >> On Thu, Jan 10, 2019, 12:36 Nick Couchman > >>> On Thu, Jan 10, 2019 at 14:59 Mike Jumper 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é jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
[GitHub] guacamole-website pull request #67: Archive releases older than 1.0.0.
GitHub user mike-jumper opened a pull request: https://github.com/apache/guacamole-website/pull/67 Archive releases older than 1.0.0. These changes archive the releases which are older than 1.0.0 (link to them only via archive.apache.org). The release layout has also been modified to add a message at the top of the release notes pointing users at the latest release if they are currently looking at the release notes of an archived release. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mike-jumper/guacamole-website archive-releases Alternatively you can review and apply these changes as the patch at: https://github.com/apache/guacamole-website/pull/67.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #67 commit 5d04c3e3ff09fc215e0f06380eeb99e1dc8f4708 Author: Michael Jumper Date: 2017-02-16T22:43:50Z Note when a release is archived. Link to latest release in older release notes. commit c7ef9422fbad701ce6998bd02defd21503779310 Author: Michael Jumper Date: 2019-01-10T06:07:46Z Link to archive.apache.org for 0.9.13-incubating and 0.9.14 releases. commit e86e41eb6bece825fb5f1761eec20796676c30b5 Author: Michael Jumper Date: 2019-01-10T06:08:35Z Mark all archived releases as such. ---
Re: [DISCUSS] Migration of git repositories to gitbox (Was: Re: [NOTICE] Mandatory migration of git repositories to gitbox.apache.org)
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 wrote: > > On Thu, Jan 10, 2019 at 14:59 Mike Jumper 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)
On Thu, Jan 10, 2019 at 15:41 Mike Jumper wrote: > On Thu, Jan 10, 2019, 12:36 Nick Couchman > > On Thu, Jan 10, 2019 at 14:59 Mike Jumper 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)
On Thu, Jan 10, 2019 at 14:59 Mike Jumper 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
[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 < infrastruct...@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: us...@infra.apache.org. > > > With regards, > Apache Infrastructure > >
