commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: [VOTE][LAZY] Migrate Apache Commons Lang to git
Date Thu, 05 Mar 2015 16:31:26 GMT
On Thu, Mar 5, 2015 at 2:13 AM, Benedikt Ritter <britter@apache.org> wrote:

> Hi,
>
> 2015-03-05 0:40 GMT+01:00 sebb AT ASF <sebb@apache.org>:
>
> > On 3 March 2015 at 17:51, Benedikt Ritter <britter@apache.org> wrote:
> > > Hi,
> > >
> > > 2015-03-01 19:04 GMT+01:00 Benedikt Ritter <britter@apache.org>:
> > >
> > >> Hello,
> > >>
> > >> 2015-01-06 18:55 GMT+01:00 sebb <sebbaz@gmail.com>:
> > >>
> > >>> On 6 January 2015 at 17:24, Benedikt Ritter <britter@apache.org>
> > wrote:
> > >>> > Hello Sebb,
> > >>> >
> > >>> > 2015-01-06 18:01 GMT+01:00 sebb <sebbaz@gmail.com>:
> > >>> >
> > >>> >> -1
> > >>> >>
> > >>> >> When the first components moved to Git, the agreement was
that
> these
> > >>> >> would be used to iron out any problems and create some
> documentation
> > >>> >> to enable developers who know SVN to migrate to Git.
> > >>> >>
> > >>> >
> > >>> > The procedure I'm following here has been discussed already [1].
> > >>>
> > >>> That was after the original discussions.
> > >>>
> > >>> >
> > >>> >>
> > >>> >> AFAICT there is no such documentation.
> > >>> >>
> > >>> >> It does not have to be extensive, just some details of commonly
> used
> > >>> >> SVN commands and their Git equivalents.
> > >>> >>
> > >>> >> For example:
> > >>> >>
> > >>> >> svn co, ci, status, diff, revert
> > >>> >> How to create a tag
> > >>> >>
> > >>> >
> > >>> > I'm not going to create such a "how to use git" documentation.
I
> > think
> > >>> > everyone of us is capable of using google, stackoverflow and man
> > pages.
> > >>> > What you're looking for may be [2].
> > >>> >
> > >>>
> > >>> Thanks, that's useful.
> > >>>
> > >>> >>
> > >>> >> Also what changes are needed to the pom.
> > >>> >>
> > >>> >
> > >>> > The only thing that has to be changed is the scm information (Luc,
> > >>> correct
> > >>> > me, if I'm wrong here).
> > >>>
> > >>> Yes, but a worked example would help.
> > >>> Git seems to have lots of different URLs for the same thing.
> > >>>
> > >>> >
> > >>> >>
> > >>> >> This would probably be best done as a Wiki page, at least
> initially.
> > >>> >>
> > >>> >
> > >>> > I think it is sufficient to update our release guide [3,4] to
> contain
> > >>> the
> > >>> > equivalent git commands.
> > >>>
> > >>> That needs to be done, yes, but I was referring to developer use of
> > >>> Git; creating and applying patches etc.
> > >>>
> > >>> > Since I'm the only one who has released [lang] for
> > >>> > a year now and the [math] people already know how to do it, I
don't
> > see
> > >>> > this as super critical. Or are you planning to RM for [lang] any
> time
> > >>> soon?
> > >>>
> > >>> No, I was not planning to RM Lang.
> > >>>
> > >>> However I would like to be able to commit fixes etc without having
to
> > >>> spend a lot of time learning new commands.
> > >>>
> > >>> > Would you be willing to withdraw your -1 if the release guide
is
> > >>> updated?
> > >>>
> > >>> Yes, of course.
> > >>>
> > >>
> > >> Sorry that this took forever, I've been busy at work. But today I
> > finally
> > >> got some time to write something together [1]. There are still two
> open
> > >> issues (retrieving all commits since the last release and git + maven
> > >> release plugin). I'd like to ask the guys from [math] to add/correct
> > >> anything missing/wrong.
> > >>
> > >> Is this enough for you to withdraw your proposal so that I can
> announce
> > >> this lazy vote as passed?
> > >>
> > >
> > > I've have published my changes to the release process documentation. I
> > > don't see a point in delaying this any longer, but I would feel better
> if
> > > sebb would comment on this once again, since he raised -1.
> >
> > I've just had a look at
> >
> > http://commons.apache.org/releases/prepare.html
> > and
> > http://commons.apache.org/releases/release.html
> >
> > I don't think they are quite ready.
> >
> > The prepare page has a missing entry "TODO: Equivalent for git "
> > This needs to be fleshed out please.
> >
> > It also says:
> >
> > >>>
> > Commons components [have] no need for a release branch ...
> > All components using git should always use a release branch.
> > If a release branch is taken then work will be required to merge any
> > changes back into the trunk.
> > <<<
> >
> > The above does not explain why a release branch is needed when using
> > Git, given that it appears to require additional work.
> >
> > >>>
> > Creating a release branch with git
> >
> > All git specific commands in the description below assume that you're
> > on the release branch.
> >
> >         git checkout -b release
> > <<<
> >
> > I don't understand what "you're on the release branch" means.
> > Is that what the checkout command does? If so, does it have to be done
> > in an empty directory?
> > What is the command to create the release branch?
> > How does one name a release branch in git?
> >
> > The release.html page syas:
> >
> > "Final tag when using git"
> >
> > Do the subsequent commands need to be done in a particular location,
> > e.g. a clean directory?
> >
>
> I'm feel pretty frustrated and left alone. I don't know the details of
> releasing lang with git (yet). I will have to figure out that when I'm
> doing it the first time. Math has already shown, that it is possible. I
> don't understand why you keep asking for explanation of git commands, which
> are well documented on the web. Give this proposal a chance. We're a patchy
> community and will figure this stuff out.
>

I'm sorry you are having a tough time. I think we'll get there eventually.
As mentioned by someone else, the git instructions do not need to be
perfect (can they be?).  For me, the svn instructions are not perfect. I
end up keeping a log of commands and gymnastics needed to do a release. Our
release process is painful, no matter the VCS. Hopefully, it won't be more
painful with Git.

Gary

>
>
> >
> > > Thanks you!
> > > Benedikt
> > >
> > >
> > >>
> > >> TIA!
> > >> Benedikt
> > >>
> > >> [1] http://svn.apache.org/r1663139
> > >>
> > >>
> > >>>
> > >>> > Regards,
> > >>> > Benedikt
> > >>> >
> > >>> > [1] http://markmail.org/message/gtbdy4ozqcogerfi
> > >>> > [2] http://git.or.cz/course/svn.html
> > >>> > [3] http://commons.apache.org/releases/prepare.html
> > >>> > [4] http://commons.apache.org/releases/release.html
> > >>> >
> > >>> >
> > >>> >>
> > >>> >>
> > >>> >>
> > >>> >> On 3 January 2015 at 12:28, Benedikt Ritter <britter@apache.org>
> > >>> wrote:
> > >>> >> > Hi all,
> > >>> >> >
> > >>> >> > since we made first (good?) experiences with Commons
Math using
> > git
> > >>> as
> > >>> >> > primary VCS, I'd like to call a vote to migrate Commons
Lang to
> > git.
> > >>> >> >
> > >>> >> > This vote by lazy consensus will close no sooner than
72 hours
> > from
> > >>> now,
> > >>> >> > i.e. after 2014/01/06 13:30 CET.
> > >>> >> >
> > >>> >> > Thanks,
> > >>> >> > Benedikt
> > >>> >> >
> > >>> >> > --
> > >>> >> > http://people.apache.org/~britter/
> > >>> >> > http://www.systemoutprintln.de/
> > >>> >> > http://twitter.com/BenediktRitter
> > >>> >> > http://github.com/britter
> > >>> >>
> > >>> >>
> > ---------------------------------------------------------------------
> > >>> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > >>> >> For additional commands, e-mail: dev-help@commons.apache.org
> > >>> >>
> > >>> >>
> > >>> >
> > >>> >
> > >>> > --
> > >>> > http://people.apache.org/~britter/
> > >>> > http://www.systemoutprintln.de/
> > >>> > http://twitter.com/BenediktRitter
> > >>> > http://github.com/britter
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > >>> For additional commands, e-mail: dev-help@commons.apache.org
> > >>>
> > >>>
> > >>
> > >>
> > >> --
> > >> http://people.apache.org/~britter/
> > >> http://www.systemoutprintln.de/
> > >> http://twitter.com/BenediktRitter
> > >> http://github.com/britter
> > >>
> > >
> > >
> > >
> > > --
> > > http://people.apache.org/~britter/
> > > http://www.systemoutprintln.de/
> > > http://twitter.com/BenediktRitter
> > > http://github.com/britter
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter
>



-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition
<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message