Re: Moving Lucene / Solr from SVN to Git

A week after sounds fine. We want to get it done before the 6.0 release and that is coming right up. - Mark On Fri, Jan 15, 2016 at 2:31 AM Dawid Weiss wrote: > Thanks Hoss. On a related note -- I assume we have a consensus about > switching to git? If anybody has

Re: Moving Lucene / Solr from SVN to Git

: INFRA-11056: Migrate Lucene project from SVN to Git. : https://issues.apache.org/jira/browse/INFRA-11056 Mark: Infra uses non standard Jira workflows, and the last infra action was to toggle the state to "Waiting for user" -- Dawid & Uwe posted followup questions for Infra in that issue, but

Re: Moving Lucene / Solr from SVN to Git

Thanks Hoss. On a related note -- I assume we have a consensus about switching to git? If anybody has problems with the workflow, I (or others) can help, hopefully. We would need to set a date for the transition so that I can prepare the repo mirror, etc. I suggest a week from when we clear how to

Re: Moving Lucene / Solr from SVN to Git

Thanks for finally switching, I have been looking forward to this. I've been doing release management and generally helping with the switch from SVN to Git for the Hibernate project in the past 5 years, so I'm happy to share hints and tips from our experience there. Feel free to ask me for help

Re: Moving Lucene / Solr from SVN to Git

Remember github is an external service, if it vanishes so would all comments and discussion. I'd stick with Jira, at least for the time being (until people get more familiar with git). Not everything at once. Dawid On Mon, Jan 11, 2016 at 9:11 AM, Shai Erera wrote: > I think

Re: Moving Lucene / Solr from SVN to Git

I think it will be nice if we integrate a code review tool into our workflow, such as Gerrit maybe (even Github pull requests are good), instead of the patch workflow with JIRA. But I agree we don't have to change that, not at start at least. The move to git will allow those who want it, to use

Re: Moving Lucene / Solr from SVN to Git

All discussion in the Github PR is captured in JIRA if the two are linked, see https://issues.apache.org/jira/browse/SOLR-8166 as an example If they are not linked, comments go to the dev list. So we can keep it as today - allow people to choose freely to use patches and/or PRs. NOTE: We should

Re: Moving Lucene / Solr from SVN to Git

I don't think there is a current plan to change how we do business. Just a change in where the master copy is hosted. We already have JIRA, dev, commit procedures, and integration with GitHub pull requests. All that will stay the same. No need to overthink it. - Mark On Sun, Jan 10, 2016 at

Re: Moving Lucene / Solr from SVN to Git

orkflows how to merge between master/trunk and the >>>> > release >>>> > branches. Projects do this in different ways (cherry-picking,…). I >>>> > have no >>>> > preference or idea, sorry! I only know how to merge feature branch

Re: Moving Lucene / Solr from SVN to Git

; Policeman > >>>> > Jenkins and fix the remaining validation tasks. I don’t want to do > >>>> > this. I > >>>> > think your commit is fine. > >>>> > > >>>> > > >&g

Re: Moving Lucene / Solr from SVN to Git

M, Uwe Schindler <u...@thetaphi.de> >> >>>> wrote: >> >>>> > Hi Mark, >> >>>> > >> >>>> > >> >>>> > >> >>>> > thanks for starting this! Looking forward to the whole process. &

Re: Moving Lucene / Solr from SVN to Git

those changes into 5x (well, maybe 6.0 by then) > >> >>>> outlined... > >> >>>> > >> >>>> Or I'm off in the weeds here, always a possibility. > >> >>>> > >> >>>> FWIW, > >> >>&

Re: Moving Lucene / Solr from SVN to Git

Will anybody be able to create a pull request and then only committers perform the merge operation? (I presume so, but... just for clarity, especially for those not git-savvy yet.) Would patches still be added to Jira requests, or simply a link to a pull request? (Again, I presume the latter, but

Re: Moving Lucene / Solr from SVN to Git

> The problem I've had with Git is not that the basic model is hard to > understand -- it's that the basic model seems inadequate for many things, so > there's been a huge proliferation of mysterious switches that are poorly Can you give an example when it's "not adequate"? For what it's worth --

Moving Lucene / Solr from SVN to Git

We have done almost all of the work necessary for a move and I have filed an issue with INFRA. LUCENE-6937: Migrate Lucene project from SVN to Git. https://issues.apache.org/jira/browse/LUCENE-6937 INFRA-11056: Migrate Lucene project from SVN to Git.

RE: Moving Lucene / Solr from SVN to Git

- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen <http://www.thetaphi.de/> http://www.thetaphi.de eMail: u...@thetaphi.de From: Mark Miller [mailto:markrmil...@gmail.com] Sent: Saturday, January 09, 2016 10:55 PM To: java-dev <java-...@lucene.apache.org> Subject: Moving Lucene

RE: Moving Lucene / Solr from SVN to Git

phi.de/> http://www.thetaphi.de eMail: u...@thetaphi.de From: Uwe Schindler [mailto:u...@thetaphi.de] Sent: Saturday, January 09, 2016 11:53 PM To: dev@lucene.apache.org Subject: RE: Moving Lucene / Solr from SVN to Git Hi Mark, thanks for starting this! Looking forward to the whole proc

Re: Moving Lucene / Solr from SVN to Git

,…). I >>> have no >>> > preference or idea, sorry! I only know how to merge feature branches >>> into >>> > master J >>> > >>> > >>> > >>> > You mentioned that we should make the old svn read only. Maybe do it >>>

Re: Moving Lucene / Solr from SVN to Git

gt; - > > Uwe Schindler > > H.-H.-Meier-Allee 63, D-28213 Bremen > > http://www.thetaphi.de > > eMail: u...@thetaphi.de > > > > From: Mark Miller [mailto:markrmil...@gmail.com] > Sent: Saturday, January 09, 2016 10:55 PM > To: java-dev <java-...@lucene.apache

Re: Moving Lucene / Solr from SVN to Git

s think? > > > > > > > > Uwe > > > > > > > > - > > > > Uwe Schindler > > > > H.-H.-Meier-Allee 63, D-28213 Bremen > > > > http://www.thetaphi.de > > > > eMail: u...@thetaphi.de > > > > &

Re: Moving Lucene / Solr from SVN to Git

le in trunk and branch_5x >> > pointing to Git. All other branches stay alive. After that we could >> make it >> > read only – but it is not really needed. What do others think? >> > >> > >> > >> > Uwe >> > >> > >&g

Re: Moving Lucene / Solr from SVN to Git

; > like we did during LuSolr merge: Add a final commit removing everything from > > trunk/branch_5x and leaving a readme.txt file in trunk and branch_5x > > pointing to Git. All other branches stay alive. After that we could make it > > read only – but it is not really needed. What do

Re: Moving Lucene / Solr from SVN to Git

t; >> > You mentioned that we should make the old svn read only. Maybe do it >> > similar >> > like we did during LuSolr merge: Add a final commit removing everything >> > from >> > trunk/branch_5x and leaving a readme.txt file in trunk and branch