[NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

2018-12-07 Thread Daniel Gruno 

[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
 DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]

Hello Apache projects,

I am writing to you because you may have git repositories on the
git-wip-us server, which is slated to be decommissioned in the coming
months. All repositories will be moved to the new gitbox service which
includes direct write access on github as well as the standard ASF
commit access via gitbox.apache.org.

## Why this move? ##
The move comes as a result of retiring the git-wip service, as the
hardware it runs on is longing for retirement. In lieu of this, we
have decided to consolidate the two services (git-wip and gitbox), to
ease the management of our repository systems and future-proof the
underlying hardware. The move is fully automated, and ideally, nothing
will change in your workflow other than added features and access to
GitHub.

## Timeframe for relocation ##
Initially, we are asking that projects voluntarily request to move
their repositories to gitbox, hence this email. The voluntary
timeframe is between now and January 9th 2019, during which projects
are free to either move over to gitbox or stay put on git-wip. After
this phase, we will be requiring the remaining projects to move within
one month, after which we will move the remaining projects over.

To have your project moved in this initial phase, you will need:

- Consensus in the project (documented via the mailing list)
- File a JIRA ticket with INFRA to voluntarily move your project repos
  over to gitbox (as stated, this is highly automated and will take
  between a minute and an hour, depending on the size and number of
  your repositories)

To sum up the preliminary timeline;

- December 9th 2018 -> January 9th 2019: Voluntary (coordinated)
  relocation
- January 9th -> February 6th: Mandated (coordinated) relocation
- February 7th: All remaining repositories are mass migrated.

This timeline may change to accommodate various scenarios.

## Using GitHub with ASF repositories ##
When your project has moved, you are free to use either the ASF
repository system (gitbox.apache.org) OR GitHub for your development
and code pushes. To be able to use GitHub, please follow the primer
at: https://reference.apache.org/committer/github


We appreciate your understanding of this issue, and hope that your
project can coordinate voluntarily moving your repositories in a
timely manner.

All settings, such as commit mail targets, issue linking, PR
notification schemes etc will automatically be migrated to gitbox as
well.

With regards, Daniel on behalf of ASF Infra.

PS:For inquiries, please reply to us...@infra.apache.org, not your 
project's dev list :-).




-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: GIT migration complete

2016-01-24 Thread Daniel Gruno 
You can't merge directly on GitHub - they only host a read-only mirror of the 
repo.
There are however command-line options for merging, which you can see on the PR 
page.
Other than that, you can mark something as merged by putting "This fixes (or 
closes, merges etc) #1234" where 1234 is the issue or PR number.

With regards,
Daniel.

On 2016-01-24 04:59, Joel Bernstein  wrote: 
> I had no problem pushing my first commit. But I didn't seem to have
> permission to merge a pull-request from Github. Is there another layer of
> permissions that need to be setup for this?
> 
> Joel Bernstein
> http://joelsolr.blogspot.com/
> 
> On Sat, Jan 23, 2016 at 1:23 PM, Yonik Seeley  wrote:
> 
> > Here's a useful thing you can add to your .profile , it conditionally
> > displays the branch you are on in your shell prompt:
> > https://gist.github.com/yonik/04b2e759eecf5ef96383
> >
> > Example:
> >
> > /opt/code$ cd lusolr
> > [master] /opt/code/lusolr$
> >
> > -Yonik
> >
> >
> > On Sat, Jan 23, 2016 at 12:55 PM, Ramkumar R. Aiyengar
> >  wrote:
> > > Not a big deal, but guys, do check if your mail is set properly in
> > > ~/.gitconfig, otherwise commits would show your personal mail as the
> > author.
> > > Committer still shows up as your apache mail address, but many UIs hide
> > it
> > > by default, and might not be apparent to those new to the project/git..
> > >
> > > Example .gitconfig snippet allowing you to keep your existing name/mail
> > but
> > > override for apache.org..
> > >
> > > [user "https://git-wip-us.apache.org;]
> > > name = Ramkumar Aiyengar
> > > mail = andyetitmo...@apache.org
> > >
> > >
> > > On Sat, Jan 23, 2016 at 3:41 PM, Uwe Schindler  wrote:
> > >>
> > >> Hi,
> > >>
> > >> I migrated all Policeman and ASF Jenkins Jobs to Git. Everything should
> > be
> > >> set up now.
> > >> The Jobs for 5.3 and 5.4 were deleted.
> > >>
> > >> Uwe
> > >>
> > >> -
> > >> Uwe Schindler
> > >> H.-H.-Meier-Allee 63, D-28213 Bremen
> > >> http://www.thetaphi.de
> > >> eMail: u...@thetaphi.de
> > >>
> > >>
> > >> > -Original Message-
> > >> > From: Uwe Schindler [mailto:u...@thetaphi.de]
> > >> > Sent: Saturday, January 23, 2016 11:05 AM
> > >> > To: dev@lucene.apache.org
> > >> > Subject: RE: GIT migration complete
> > >> >
> > >> > Hi,
> > >> >
> > >> > Thanks! I am talking care of Jenkins at the moment.
> > >> >
> > >> > First Policeman one is working:
> > >> > http://jenkins.thetaphi.de/job/Lucene-Solr-
> > >> > trunk-Linux/15619/console
> > >> >
> > >> > The Changes I do for jenkins is:
> > >> > - Deleted *all* workspaces to have clean start
> > >> > - Change all Jobs (is a bit of work as manually, especially for ASF)
> > to
> > >> > use Git
> > >> > checkouts of corresponding branch
> > >> > - Add the following "additional behaviour" config: Clean before
> > >> > checkout:
> > >> > Clean up the workspace before every checkout by deleting all untracked
> > >> > files
> > >> > and directories, including those which are specified in .gitignore. It
> > >> > also resets
> > >> > all tracked files to their versioned state. This ensures that the
> > >> > workspace is in
> > >> > the same state as if you cloned and checked out in a brand-new empty
> > >> > directory, and ensures that your build is not affected by the files
> > >> > generated
> > >> > by the previous build.
> > >> >
> > >> > Uwe
> > >> >
> > >> > -
> > >> > Uwe Schindler
> > >> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > >> > http://www.thetaphi.de
> > >> > eMail: u...@thetaphi.de
> > >> >
> > >> > > From: Dawid Weiss [mailto:dawid.we...@gmail.com]
> > >> > > Sent: Saturday, January 23, 2016 10:13 AM
> > >> > > To: dev@lucene.apache.org
> > >> > > Subject: GIT migration complete
> > >> > >
> > >> > > Ok, folks. Seems like code migration is complete, with both gh
> > mirrors
> > >> > > and Apache repos up.
> > >> > >
> > >> > > 1. Please read the docs at: https://git-wip-us.apache.org/
> > >> > >
> > >> > > 2. I didn't realize Apache's repositories are over https, which
> > makes
> > >> > > authorization rather painful for Linux users (requires password
> > typing
> > >> > > on every push). I think I'll stick with gh for this reason and only
> > >> > > push my changes when they're fully baked.
> > >> > >
> > >> > > 3. The master branch (former trunk) passes ant precommit for me,
> > but I
> > >> > > didn't apply build patches to branch_5x yet.
> > >> > >
> > >> > > If there are any problems or concerns, let me know (perhaps I'll be
> > >> > > able to help).
> > >> > >
> > >> > > Dawid
> > >> > >
> > >> > >
> > -
> > >> > > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> > >> > > For additional commands, e-mail: dev-h...@lucene.apache.org
> > >> >
> > >> >
> > >> > -
> > >> > To unsubscribe, e-mail:

Re: Apache Lucene/Solr GIT migration, requesting infra help

2016-01-23 Thread Daniel Gruno 
Just a heads up: Everything is working now and GitHub has caught up with
the new repository. You should be good to go :)

With regards,
Daniel.

On 01/23/2016 08:36 AM, Daniel Gruno wrote:
> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
>> Hello Daniel,
>>
>> I've prepared everything for the migration and I hand it off to you (I
>> will be available in the morning, if you need assistance). I can also
>> log on to hipchat, but send me an e-mail if you wish me to.
>>
>> Here are the steps we kindly ask you to perform (I allowed myself to
>> uppercase certain things, apologies if it looks like shouting):
>>
>> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
>> are obsolete and incorrect syncs, consolidated git repo contains full
>> history):
>>
>> git://git.apache.org/solr.git
> DONE
> 
>> git://git.apache.org/lucene.git
> DONE
>>
>> 2) Notify (somehow) GitHub that these two repos have been removed
>> (they should not be available or visible on GitHub as well):
>>
>> https://github.com/apache/lucene
> DONE
>> https://github.com/apache/solr
> DONE
> 
>>
>> 3) DISABLE svn syncing for the following git mirror:
>>
>> git://git.apache.org/lucene-solr.git
> DONE
> 
>>
>> and then REPLACE it (wipe it clean) with the content of the following
>> consolidated repository:
>>
>> g...@github.com:dweiss/lucene-solr-svn2git.git
>>
>> I don't know how it looks from the backend's side, but this should
>> also work, if there are sufficient permissions:
>>
>> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
>> git remote add apache git://git.apache.org/lucene-solr.git
>> git push --mirror apache
> We have our own methods, but nonetheless DONE. Please check that you
> have write-access to the new repo.
>>
>> 4) I don't know if we need to make GitHub aware of the replaced
>> content of the lucene-solr repo or if their syncing will handle this
>> automatically. It would be nice if they could catch up as quickly as
>> possible.
> 
> As explained on the JIRA ticket, if we're lucky, this should happen
> automagically in about 20 minutes from now. If not, we'll have to wait
> 24 hours. Time will tell :)
> 
> With regards,
> Daniel.
> 
>>
>> In case of questions, problems or a successful import, please drop me
>> an e-mail. Oh, thank you for being so nice and helping us on your day
>> off -- much appreciated.
>>
>> Dawid
>>
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Apache Lucene/Solr GIT migration, requesting infra help

2016-01-23 Thread Daniel Gruno 
On 01/23/2016 09:53 AM, Shalin Shekhar Mangar wrote:
> Thanks Dawid and Daniel for all the work!
> 
> One strange thing that I noticed is that my fork of apache/lucene-solr
> at https://github.com/shalinmangar/lucene-solr is now shown to be a
> fork of https://github.com/mdodsworth/lucene-solr. I have no idea who
> that guy is. What can we do to fix this?

Nothing. This is GitHub's fallback method when the original repository
goes away as it did here (replaced with a new repo with a new history).
Since referring to the old repo which doesn't exist anymore would break
your copy, they have fallen back to another copy of it.

Please re-fork.

With regards,
Daniel.

> 
> On Sat, Jan 23, 2016 at 2:05 PM, Dawid Weiss <dawid.we...@gmail.com> wrote:
>> 1. The content of the lucene-solr.git repository looks good!
>>
>> 2) PROBLEM. I can't push my own branch:
>>
>> $ git co master -b git-check
>> $ [... committed a dummy commit ]
>> $ git push origin HEAD -u
>> fatal: remote error: access denied or repository not exported: 
>> /lucene-solr.git
>>
>> 3) Solr repo is still available for some reason, both as real git repo here:
>>
>> git://git.apache.org/solr.git
>>
>> and listed here:
>>
>> https://git.apache.org/
>>
>> Could I be seeing a mirror or something?
>>
>> Dawid
>>
>>
>> On Sat, Jan 23, 2016 at 9:22 AM, Dawid Weiss <dawid.we...@gmail.com> wrote:
>>> Checking everything now -- that was fast Daniel!
>>> Dawid
>>>
>>>
>>> On Sat, Jan 23, 2016 at 9:05 AM, Daniel Gruno <humbed...@apache.org> wrote:
>>>> Just a heads up: Everything is working now and GitHub has caught up with
>>>> the new repository. You should be good to go :)
>>>>
>>>> With regards,
>>>> Daniel.
>>>>
>>>> On 01/23/2016 08:36 AM, Daniel Gruno wrote:
>>>>> On 01/23/2016 03:02 AM, Dawid Weiss wrote:
>>>>>> Hello Daniel,
>>>>>>
>>>>>> I've prepared everything for the migration and I hand it off to you (I
>>>>>> will be available in the morning, if you need assistance). I can also
>>>>>> log on to hipchat, but send me an e-mail if you wish me to.
>>>>>>
>>>>>> Here are the steps we kindly ask you to perform (I allowed myself to
>>>>>> uppercase certain things, apologies if it looks like shouting):
>>>>>>
>>>>>> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
>>>>>> are obsolete and incorrect syncs, consolidated git repo contains full
>>>>>> history):
>>>>>>
>>>>>> git://git.apache.org/solr.git
>>>>> DONE
>>>>>
>>>>>> git://git.apache.org/lucene.git
>>>>> DONE
>>>>>>
>>>>>> 2) Notify (somehow) GitHub that these two repos have been removed
>>>>>> (they should not be available or visible on GitHub as well):
>>>>>>
>>>>>> https://github.com/apache/lucene
>>>>> DONE
>>>>>> https://github.com/apache/solr
>>>>> DONE
>>>>>
>>>>>>
>>>>>> 3) DISABLE svn syncing for the following git mirror:
>>>>>>
>>>>>> git://git.apache.org/lucene-solr.git
>>>>> DONE
>>>>>
>>>>>>
>>>>>> and then REPLACE it (wipe it clean) with the content of the following
>>>>>> consolidated repository:
>>>>>>
>>>>>> g...@github.com:dweiss/lucene-solr-svn2git.git
>>>>>>
>>>>>> I don't know how it looks from the backend's side, but this should
>>>>>> also work, if there are sufficient permissions:
>>>>>>
>>>>>> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
>>>>>> git remote add apache git://git.apache.org/lucene-solr.git
>>>>>> git push --mirror apache
>>>>> We have our own methods, but nonetheless DONE. Please check that you
>>>>> have write-access to the new repo.
>>>>>>
>>>>>> 4) I don't know if we need to make GitHub aware of the replaced
>>>>>> content of the lucene-solr repo or if their syncing will handle this
>>>>>> automatically. It would be nice if they could catch up as quickly as
>>>>>> possible.
>>>>>
>>>>> As explained on the JIRA ticket, if we're lucky, this should happen
>>>>> automagically in about 20 minutes from now. If not, we'll have to wait
>>>>> 24 hours. Time will tell :)
>>>>>
>>>>> With regards,
>>>>> Daniel.
>>>>>
>>>>>>
>>>>>> In case of questions, problems or a successful import, please drop me
>>>>>> an e-mail. Oh, thank you for being so nice and helping us on your day
>>>>>> off -- much appreciated.
>>>>>>
>>>>>> Dawid
>>>>>>
>>>>>
>>>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: dev-h...@lucene.apache.org
>>
> 
> 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Re: Apache Lucene/Solr GIT migration, requesting infra help

2016-01-22 Thread Daniel Gruno 
On 01/23/2016 03:02 AM, Dawid Weiss wrote:
> Hello Daniel,
> 
> I've prepared everything for the migration and I hand it off to you (I
> will be available in the morning, if you need assistance). I can also
> log on to hipchat, but send me an e-mail if you wish me to.
> 
> Here are the steps we kindly ask you to perform (I allowed myself to
> uppercase certain things, apologies if it looks like shouting):
> 
> 1) Permanently REMOVE the following git mirrors of SVN (reason: they
> are obsolete and incorrect syncs, consolidated git repo contains full
> history):
> 
> git://git.apache.org/solr.git
DONE

> git://git.apache.org/lucene.git
DONE
> 
> 2) Notify (somehow) GitHub that these two repos have been removed
> (they should not be available or visible on GitHub as well):
> 
> https://github.com/apache/lucene
DONE
> https://github.com/apache/solr
DONE

> 
> 3) DISABLE svn syncing for the following git mirror:
> 
> git://git.apache.org/lucene-solr.git
DONE

> 
> and then REPLACE it (wipe it clean) with the content of the following
> consolidated repository:
> 
> g...@github.com:dweiss/lucene-solr-svn2git.git
> 
> I don't know how it looks from the backend's side, but this should
> also work, if there are sufficient permissions:
> 
> git clone g...@github.com:dweiss/lucene-solr-svn2git.git
> git remote add apache git://git.apache.org/lucene-solr.git
> git push --mirror apache
We have our own methods, but nonetheless DONE. Please check that you
have write-access to the new repo.
> 
> 4) I don't know if we need to make GitHub aware of the replaced
> content of the lucene-solr repo or if their syncing will handle this
> automatically. It would be nice if they could catch up as quickly as
> possible.

As explained on the JIRA ticket, if we're lucky, this should happen
automagically in about 20 minutes from now. If not, we'll have to wait
24 hours. Time will tell :)

With regards,
Daniel.

> 
> In case of questions, problems or a successful import, please drop me
> an e-mail. Oh, thank you for being so nice and helping us on your day
> off -- much appreciated.
> 
> Dawid
> 


-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org