You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Lukasz Lenart <lu...@apache.org> on 2013/12/06 08:11:37 UTC
Re: Svn to Git migration
Do you know if git at Apache supports Pull Requests between branches?
I've started working like that some time ago and it's awesome feature :-)
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/10/16 Christian Grobmeier <gr...@gmail.com>:
> On 16 Oct 2013, at 10:50, Lukasz Lenart wrote:
>
>> As far as I know, SvnPubSub doesn't support Git right now. So we can
>> migrate struts2/trunk to Git but the rest must stay as is. And if we
>> plan to migrate/create new user guide, it will be hosted via
>> Subversion. Any doubts?
>
>
> +1
>
>
>
>
>
>
>
>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>>
>> 2013/9/18 Rene Gielen <re...@gmail.com>:
>>>
>>> +1
>>>
>>> Am 18.09.13 11:38, schrieb Lukasz Lenart:
>>>>
>>>> When 2.3.15.2 will be officially out, I want to send request to Infra
>>>> for Svn to Git migration
>>>>
>>>> 2013/9/17 Christian Grobmeier <gr...@gmail.com>:
>>>>>
>>>>> thats fine :-) Now as we have that agreement, let's keep us moving :)
>>>>>
>>>>> Am 17.09.13 22:48, schrieb Rene Gielen:
>>>>>>
>>>>>> I just wanted to get this clarified. Seems like we have an agreement
>>>>>> :-)
>>>>>> Am 17.09.2013 21:14 schrieb "Christian Grobmeier"
>>>>>> <gr...@gmail.com>:
>>>>>>
>>>>>>> Am 17.09.13 21:06, schrieb Johannes Geppert:
>>>>>>>>>
>>>>>>>>> -1 for moving trunk only. We don't want to lose history, and we
>>>>>>>>> would
>>>>>>>>> not want two repositories for one project (Struts 2). Once we moved
>>>>>>>>> to
>>>>>>>>> git, the full struts2 svn tree should either be switched to
>>>>>>>>> read-only
>>>>>>>>> or/and later be removed.
>>>>>>>>
>>>>>>>>
>>>>>>>> Sure you are right the history should not be lost.
>>>>>>>> What I mean is not to migrate the struts1, archive, sandbox
>>>>>>>> and site into the new struts.git repository.
>>>>>>>
>>>>>>>
>>>>>>> You speak of different things.
>>>>>>>
>>>>>>> This is not to migrate:
>>>>>>> http://svn.apache.org/repos/asf/struts/
>>>>>>> and I believe Jo is against migrating the content of all of that. I
>>>>>>> agree with him.
>>>>>>>
>>>>>>> We need to migrate this:
>>>>>>>
>>>>>>> http://svn.apache.org/repos/asf/struts/struts2/
>>>>>>> including branches (there are non in short time), tags and trunk.
>>>>>>>
>>>>>>> I bet you are on the same page here.
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Johannes
>>>>>>>>
>>>>>>>> #################################################
>>>>>>>> web: http://www.jgeppert.com
>>>>>>>> twitter: http://twitter.com/jogep
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> 2013/9/13 Rene Gielen <re...@gmail.com>
>>>>>>>>
>>>>>>>>> +1 for git flow as the way to go, including excellent tooling -
>>>>>>>>> command
>>>>>>>>> line extensions, Atlassian Sourcetree support and even a IDEA
>>>>>>>>> plugin
>>>>>>>>> (https://github.com/OpherV/gitflow4idea) help to make this an
>>>>>>>>> elegant
>>>>>>>>> abstract and reliable workflow.
>>>>>>>>>
>>>>>>>>> -1 for moving trunk only. We don't want to lose history, and we
>>>>>>>>> would
>>>>>>>>> not want two repositories for one project (Struts 2). Once we moved
>>>>>>>>> to
>>>>>>>>> git, the full struts2 svn tree should either be switched to
>>>>>>>>> read-only
>>>>>>>>> or/and later be removed.
>>>>>>>>>
>>>>>>>>> +1 for dealing with ../branches/STRUTS_3_X etc as hierarchical
>>>>>>>>> feature
>>>>>>>>> branches from which single feature branches will be forked for
>>>>>>>>> actual
>>>>>>>>> development - at least for now. I want to investigate further on
>>>>>>>>> this
>>>>>>>>> one, but basically there should not be a problem if we start like
>>>>>>>>> this.
>>>>>>>>>
>>>>>>>>> - René
>>>>>>>>>
>>>>>>>>> Am 12.09.13 21:48, schrieb Johannes Geppert:
>>>>>>>>>>
>>>>>>>>>> +1 for starting with the Git migration process.
>>>>>>>>>>
>>>>>>>>>> What about only migrating the current svn struts2/trunk to git and
>>>>>>>
>>>>>>> leave
>>>>>>>>>>
>>>>>>>>>> the rest in the svn repository?
>>>>>>>>>>
>>>>>>>>>> If we need sometime also the site in git we can request a separate
>>>>>>>>>> git
>>>>>>>>>> repository like struts-site.git.
>>>>>>>>>>
>>>>>>>>>> Johannes
>>>>>>>>>>
>>>>>>>>>> #################################################
>>>>>>>>>> web: http://www.jgeppert.com
>>>>>>>>>> twitter: http://twitter.com/jogep
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2013/9/11 Lukasz Lenart <lu...@apache.org>
>>>>>>>>>>
>>>>>>>>>>> Hi,
>>>>>>>>>>>
>>>>>>>>>>> I'd like to start discussion about the migration process - there
>>>>>>>>>>> are
>>>>>>>>>>> few things we must clarify, at least:
>>>>>>>>>>> - Git structure
>>>>>>>>>>> - development flow
>>>>>>>>>>>
>>>>>>>>>>> I think we should have just one repo: git.apache.org/struts.git
>>>>>>>>>>> and
>>>>>>>>>>> diverse versions internally via branches - so the current S2
>>>>>>>>>>> source
>>>>>>>>>>> become the base and then we will transfer it to 2.5 and 3 in the
>>>>>>>>>>> future.
>>>>>>>>>>>
>>>>>>>>>>> As a flow I like git-flow [1] - well known and used
>>>>>>>>>>>
>>>>>>>>>>> [1] https://github.com/nvie/gitflow
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Regards
>>>>>>>>>>> --
>>>>>>>>>>> Łukasz
>>>>>>>>>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>>>>>>>>>
>>>>>>>>>>> PS. It'll be implemented after cleaning up current pipeline :-)
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> René Gielen
>>>>>>>>> http://twitter.com/rgielen
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>
>>>
>>>
>>> --
>>> René Gielen
>>> http://twitter.com/rgielen
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>
>
>
> ---
> http://www.grobmeier.de
> @grobmeier
> GPG: 0xA5CC90DB
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Rene Gielen <gi...@it-neering.net>.
+1
Paul Benedict <pb...@apache.org> schrieb:
>No, please don't move things to the attic. We published POMs and other
>links to the repository. We should just make it read-only.
>
>
>On Tue, Jan 14, 2014 at 1:23 PM, Johannes Geppert <jo...@gmail.com>
>wrote:
>
>> Looks good to me!
>>
>> Thanks Łukasz for taking care of this migration.
>>
>> Johannes
>>
>> #################################################
>> web: http://www.jgeppert.com
>> twitter: http://twitter.com/jogep
>>
>>
>> 2014/1/14 Lukasz Lenart <lu...@apache.org>
>>
>> > Guys,
>> > can you review cleanup I have performed?
>> >
>> > https://svn.apache.org/repos/asf/struts/
>> > https://svn.apache.org/repos/asf/struts/attic/
>> >
>> > what else I should move to attic as well
>> >
>> >
>> > Regards
>> > --
>> > Łukasz
>> > + 48 606 323 122 http://www.lenart.org.pl/
>> >
>> > 2014/1/14 Lukasz Lenart <lu...@apache.org>:
>> > > I think it isn't needed. I'm going to move everything to 'attic'
>> > > folder to be backed up and create README about migration
>> > >
>> > > 2014/1/14 Paul Benedict <pb...@apache.org>:
>> > >> Can you request to turn it read only?
>> > >> On Jan 14, 2014 11:58 AM, "Lukasz Lenart"
><lu...@apache.org>
>> > wrote:
>> > >>
>> > >>> Migration to Git is almost done! Please DON'T use Subversion
>anymore!
>> > >>>
>> > >>> https://issues.apache.org/jira/browse/INFRA-7174
>> > >>>
>> > >>>
>> > >>> Regards
>> > >>> --
>> > >>> Łukasz
>> > >>> + 48 606 323 122 http://www.lenart.org.pl/
>> > >>>
>> > >>> 2014/1/9 Lukasz Lenart <lu...@apache.org>:
>> > >>> > Time to move forward
>> > >>> >
>> > >>> > https://issues.apache.org/jira/browse/INFRA-7174
>> > >>> >
>> > >>> > 2013/12/10 Christian Grobmeier <gr...@gmail.com>:
>> > >>> >> On 10 Dec 2013, at 7:55, Lukasz Lenart wrote:
>> > >>> >>
>> > >>> >>> I'm going postpone transition to Git as we must straighten
>site
>> > >>> >>> building first! Right now it's a real pain in the a.. and
>it
>> takes
>> > >>> >>> ages to update site after release. Not saying about other
>mirror
>> > >>> >>> problems with this whole SvnPubSub crap :\
>> > >>> >>
>> > >>> >>
>> > >>> >> Oh ok. :-|
>> > >>> >>
>> > >>> >> I am a bit undecided on how we approach the website (again).
>> > >>> >>
>> > >>> >>
>> > >>> >>
>> > >>> >>
>> > >>> >>>
>> > >>> >>> Regards
>> > >>> >>> --
>> > >>> >>> Łukasz
>> > >>> >>> + 48 606 323 122 http://www.lenart.org.pl/
>> > >>> >>>
>> > >>> >>> 2013/12/6 Dave Newton <da...@gmail.com>:
>> > >>> >>>>
>> > >>> >>>> Correct; pull requests are a github thing.
>> > >>> >>>>
>> > >>> >>>> And they're nice (usually).
>> > >>> >>>>
>> > >>> >>>>
>> > >>> >>>> On Fri, Dec 6, 2013 at 12:09 PM, Christian Grobmeier
>> > >>> >>>> <gr...@gmail.com>wrote:
>> > >>> >>>>
>> > >>> >>>>> On 6 Dec 2013, at 15:19, Lukasz Lenart wrote:
>> > >>> >>>>>
>> > >>> >>>>> 2013/12/6 Christian Grobmeier <gr...@gmail.com>:
>> > >>> >>>>>>
>> > >>> >>>>>>
>> > >>> >>>>>>> On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
>> > >>> >>>>>>>
>> > >>> >>>>>>> Do you know if git at Apache supports Pull Requests
>between
>> > >>> branches?
>> > >>> >>>>>>>>
>> > >>> >>>>>>>> I've started working like that some time ago and it's
>> awesome
>> > >>> feature
>> > >>> >>>>>>>> :-)
>> > >>> >>>>>>>>
>> > >>> >>>>>>>
>> > >>> >>>>>>> Honestly I don't know :-)
>> > >>> >>>>>>>
>> > >>> >>>>>>> I mean you can merge between branches easily. Is that
>what
>> you
>> > >>> mean?
>> > >>> >>>>>>>
>> > >>> >>>>>>
>> > >>> >>>>>> Not exactly, in GitHub you can prepare a Pull Request
>between
>> > >>> >>>>>> different branches in the same repo - you don't have to
>fork
>> the
>> > >>> repo
>> > >>> >>>>>> at all. So you'll see the PR on issues list and you can
>> comment,
>> > >>> >>>>>> change the code and so on, before merging it to
>mater/develop.
>> > >>> >>>>>>
>> > >>> >>>>>> But I think it's pure GitHub functionality not really
>related
>> > to git
>> > >>> >>>>>> itself.
>> > >>> >>>>>>
>> > >>> >>>>>
>> > >>> >>>>> I don't know for sure, but I agree, its most likely a
>github
>> > feature.
>> > >>> >>>>> I think something like gitlabhq might be able to do the
>same:
>> > >>> >>>>> https://github.com/gitlabhq/gitlabhq
>> > >>> >>>>> But i have not heard if this is going to live at ASF
>infra
>> > >>> >>>>>
>> > >>> >>>>>
>> > >>> >>>>>> Regards
>> > >>> >>>>>> --
>> > >>> >>>>>> Łukasz
>> > >>> >>>>>> + 48 606 323 122 http://www.lenart.org.pl/
>> > >>> >>>>>>
>> > >>> >>>>>>
>> > >>>
>---------------------------------------------------------------------
>> > >>> >>>>>> To unsubscribe, e-mail:
>dev-unsubscribe@struts.apache.org
>> > >>> >>>>>> For additional commands, e-mail:
>dev-help@struts.apache.org
>> > >>> >>>>>>
>> > >>> >>>>>
>> > >>> >>>>>
>> > >>> >>>>> ---
>> > >>> >>>>> http://www.grobmeier.de
>> > >>> >>>>> @grobmeier
>> > >>> >>>>> GPG: 0xA5CC90DB
>> > >>> >>>>>
>> > >>> >>>>>
>> >
>---------------------------------------------------------------------
>> > >>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> > >>> >>>>> For additional commands, e-mail:
>dev-help@struts.apache.org
>> > >>> >>>>>
>> > >>> >>>>>
>> > >>> >>>>
>> > >>> >>>>
>> > >>> >>>> --
>> > >>> >>>> e: davelnewton@gmail.com
>> > >>> >>>> m: 908-380-8699
>> > >>> >>>> s: davelnewton_skype
>> > >>> >>>> t: @dave_newton <https://twitter.com/dave_newton>
>> > >>> >>>> b: Bucky Bits <http://buckybits.blogspot.com/>
>> > >>> >>>> g: davelnewton <https://github.com/davelnewton>
>> > >>> >>>> so: Dave Newton <
>> > http://stackoverflow.com/users/438992/dave-newton>
>> > >>> >>>
>> > >>> >>>
>> > >>> >>>
>> >
>---------------------------------------------------------------------
>> > >>> >>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> > >>> >>> For additional commands, e-mail: dev-help@struts.apache.org
>> > >>> >>
>> > >>> >>
>> > >>> >>
>> > >>> >> ---
>> > >>> >> http://www.grobmeier.de
>> > >>> >> @grobmeier
>> > >>> >> GPG: 0xA5CC90DB
>> > >>> >>
>> > >>> >>
>> >
>---------------------------------------------------------------------
>> > >>> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> > >>> >> For additional commands, e-mail: dev-help@struts.apache.org
>> > >>> >>
>> > >>>
>> > >>>
>---------------------------------------------------------------------
>> > >>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> > >>> For additional commands, e-mail: dev-help@struts.apache.org
>> > >>>
>> > >>>
>> >
>> >
>---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> > For additional commands, e-mail: dev-help@struts.apache.org
>> >
>> >
>>
>
>
>
>--
>Cheers,
>Paul
--
Sent from my mobile phone
Re: Svn to Git migration
Posted by Lukasz Lenart <lu...@apache.org>.
Sonar reconfigured as well!
https://analysis.apache.org/dashboard/index/9936
2014/1/20 Lukasz Lenart <lu...@apache.org>:
> Readme added, is that ok?
> https://svn.apache.org/repos/asf/struts/struts2/
>
> 2014/1/20 Lukasz Lenart <lu...@apache.org>:
>> 2014/1/19 Lukasz Lenart <lu...@apache.org>:
>>> That said, I want to release new version ASAP (when code snippets will
>>> be solved).
>>>
>>> [1] https://cwiki.apache.org/confluence/display/WW/Scope+Interceptor
>>
>> All the problems with snippets solved!
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Lukasz Lenart <lu...@apache.org>.
Readme added, is that ok?
https://svn.apache.org/repos/asf/struts/struts2/
2014/1/20 Lukasz Lenart <lu...@apache.org>:
> 2014/1/19 Lukasz Lenart <lu...@apache.org>:
>> That said, I want to release new version ASAP (when code snippets will
>> be solved).
>>
>> [1] https://cwiki.apache.org/confluence/display/WW/Scope+Interceptor
>
> All the problems with snippets solved!
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Lukasz Lenart <lu...@apache.org>.
2014/1/19 Lukasz Lenart <lu...@apache.org>:
> That said, I want to release new version ASAP (when code snippets will
> be solved).
>
> [1] https://cwiki.apache.org/confluence/display/WW/Scope+Interceptor
All the problems with snippets solved!
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Lukasz Lenart <lu...@apache.org>.
2014/1/16 Paul Benedict <pb...@apache.org>:
> The only problem is that links to the old Struts source are broken. The
> "attic" is traditionally been reserved for dead projects. We're not in that
> situation. All we need is a read-only lock.
And that's very good! See [1], without moving to attic we'd discover
that just before release or (what even worse) fast-track release. I
opt to leave the source code in attic for now, at least till we
release a new version based on Git. In other case we can miss
something because there still will be an old code where it was before.
When we stabilise the new process we can move the source code back to
old location.
That said, I want to release new version ASAP (when code snippets will
be solved).
[1] https://cwiki.apache.org/confluence/display/WW/Scope+Interceptor
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Paul Benedict <pb...@apache.org>.
The only problem is that links to the old Struts source are broken. The
"attic" is traditionally been reserved for dead projects. We're not in that
situation. All we need is a read-only lock.
On Thu, Jan 16, 2014 at 1:24 AM, Lukasz Lenart <lu...@apache.org>wrote:
> I still don't get it - what is the problem with moving the source to
> attic? It isn't valid source code any more - what is valid are the
> tags (/struts2/tags/STRUTS_2_3_8) but I doubt that anybody uses them
> (except us).
>
> Wicket - very good example, I didn't know it isn't valid source code
> anymore (I have been checking it few times how they solved issues with
> SvnPubSub - I was waisting my time). There should be huge banner -
> MOVED-TO-GIT-DONT-USE-THIS-SOURCE!
>
> So, I opt to leave the source in attic and react if users start
> complaining about that.
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2014/1/15 Rene Gielen <re...@gmail.com>:
> > I wonder what the downside is to just put svn subtrees in question into
> > read only mode compared to moving them to attic. As for placing a
> > prominent notice, such as MOVED-TO-GIT-README.txt, it would be useful to
> > our users in either case.
> >
> > Having a look at wicket, they just left svn at a point in time, keeping
> > everything in place (presumably read-only):
> > http://svn.apache.org/repos/asf/wicket/
> > While I would wish to find a prominent README here as described above, a
> > see a case for not breaking things that are not in our hand. In the
> > early days of Weld / CDI e.g., I desperately needed trunk level builds
> > that were not published yet. For that reason I did a
> > checkout-and-build-dependency step in the maven bootstrap phase of my
> > build. While this was clearly violating the reproducible build
> > principle, I could live with this trade-off since the features I needed
> > were additions unlikely to go away. To some extent reproducibility may
> > be seen as that if you would checkout some project published a few years
> > ago, it would build without some early failures before javac even kicks
> > in. I know this is a corner case, but it would suffer from repo contents
> > (from which a checkout would be done during my build) being moved away.
> >
> > Regarding Apache policies, there are a few around that might help
> > finding a decision:
> > - Apache requires us to run on our own infrastructure for a single
> > reason: provide resources that will last for ages at the same place.
> > That is why we would not want to do canonical hosting of projects
> > externally, such as on GitHub - maybe it shuts down tomorrow? Unlikely,
> > yes. On the other hand, we have seen such things happen: tr.im URL
> > shortener was popular by it's time, but then money ran out. Each mailing
> > list posting containing tr.im URL you will look up in archive render
> > useless due to the URLs cannot be resolved any more. That's why Apache
> > even promotes their own URL shortener, http://s.apache.org.
> > - Dead projects, that is projects with dead communities, go to the Attic
> > meta project, including move of svn resources. While this has more to do
> > with having a meta-PMC for keeping oversight even if the owning PMC is
> > dead, it indeed involves moving of svn resources - AFAIK the only
> > process where such move happens as a part of an Apache policy. So moving
> > something to something called "attic" makes me shout out "I'm not dead
> > yet!" spontaneously :)
> >
> > So far, I would really tend to go into read-only mode with notices
> > placed in svn rather than to move things away. If there are good
> > arguments for the move I have missed so far, I would of course happily
> > switch my position on that topic.
> >
> > Just my 0.02$
> > - René
> >
> > Am 15.01.14 20:54, schrieb Lukasz Lenart:
> >> 2014/1/15 Paul Benedict <pb...@apache.org>:
> >>> The published POMs should all have a link to the SCM URL. We shouldn't
> move
> >>> to the attic so those links can stay valid.
> >>
> >> Ok, what is wrong if they become invalid? Maybe people start thinking
> >> about migration :-)
> >>
> >>> And what do you mean "cut the wire"? Is that an Apache directive to
> stop
> >>> people from going to svn?
> >>
> >> I don't know how it is in English - when child is born, connection
> >> with mother is cut :-) The same here, at some point we must strictly
> >> say - sorry guys!
> >>
> >> It was mentioned as a good practise from other projects which migrated
> to Git.
> >>
> >>
> >> Regards
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
Cheers,
Paul
Re: Svn to Git migration
Posted by Lukasz Lenart <lu...@apache.org>.
I still don't get it - what is the problem with moving the source to
attic? It isn't valid source code any more - what is valid are the
tags (/struts2/tags/STRUTS_2_3_8) but I doubt that anybody uses them
(except us).
Wicket - very good example, I didn't know it isn't valid source code
anymore (I have been checking it few times how they solved issues with
SvnPubSub - I was waisting my time). There should be huge banner -
MOVED-TO-GIT-DONT-USE-THIS-SOURCE!
So, I opt to leave the source in attic and react if users start
complaining about that.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2014/1/15 Rene Gielen <re...@gmail.com>:
> I wonder what the downside is to just put svn subtrees in question into
> read only mode compared to moving them to attic. As for placing a
> prominent notice, such as MOVED-TO-GIT-README.txt, it would be useful to
> our users in either case.
>
> Having a look at wicket, they just left svn at a point in time, keeping
> everything in place (presumably read-only):
> http://svn.apache.org/repos/asf/wicket/
> While I would wish to find a prominent README here as described above, a
> see a case for not breaking things that are not in our hand. In the
> early days of Weld / CDI e.g., I desperately needed trunk level builds
> that were not published yet. For that reason I did a
> checkout-and-build-dependency step in the maven bootstrap phase of my
> build. While this was clearly violating the reproducible build
> principle, I could live with this trade-off since the features I needed
> were additions unlikely to go away. To some extent reproducibility may
> be seen as that if you would checkout some project published a few years
> ago, it would build without some early failures before javac even kicks
> in. I know this is a corner case, but it would suffer from repo contents
> (from which a checkout would be done during my build) being moved away.
>
> Regarding Apache policies, there are a few around that might help
> finding a decision:
> - Apache requires us to run on our own infrastructure for a single
> reason: provide resources that will last for ages at the same place.
> That is why we would not want to do canonical hosting of projects
> externally, such as on GitHub - maybe it shuts down tomorrow? Unlikely,
> yes. On the other hand, we have seen such things happen: tr.im URL
> shortener was popular by it's time, but then money ran out. Each mailing
> list posting containing tr.im URL you will look up in archive render
> useless due to the URLs cannot be resolved any more. That's why Apache
> even promotes their own URL shortener, http://s.apache.org.
> - Dead projects, that is projects with dead communities, go to the Attic
> meta project, including move of svn resources. While this has more to do
> with having a meta-PMC for keeping oversight even if the owning PMC is
> dead, it indeed involves moving of svn resources - AFAIK the only
> process where such move happens as a part of an Apache policy. So moving
> something to something called "attic" makes me shout out "I'm not dead
> yet!" spontaneously :)
>
> So far, I would really tend to go into read-only mode with notices
> placed in svn rather than to move things away. If there are good
> arguments for the move I have missed so far, I would of course happily
> switch my position on that topic.
>
> Just my 0.02$
> - René
>
> Am 15.01.14 20:54, schrieb Lukasz Lenart:
>> 2014/1/15 Paul Benedict <pb...@apache.org>:
>>> The published POMs should all have a link to the SCM URL. We shouldn't move
>>> to the attic so those links can stay valid.
>>
>> Ok, what is wrong if they become invalid? Maybe people start thinking
>> about migration :-)
>>
>>> And what do you mean "cut the wire"? Is that an Apache directive to stop
>>> people from going to svn?
>>
>> I don't know how it is in English - when child is born, connection
>> with mother is cut :-) The same here, at some point we must strictly
>> say - sorry guys!
>>
>> It was mentioned as a good practise from other projects which migrated to Git.
>>
>>
>> Regards
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Rene Gielen <re...@gmail.com>.
I wonder what the downside is to just put svn subtrees in question into
read only mode compared to moving them to attic. As for placing a
prominent notice, such as MOVED-TO-GIT-README.txt, it would be useful to
our users in either case.
Having a look at wicket, they just left svn at a point in time, keeping
everything in place (presumably read-only):
http://svn.apache.org/repos/asf/wicket/
While I would wish to find a prominent README here as described above, a
see a case for not breaking things that are not in our hand. In the
early days of Weld / CDI e.g., I desperately needed trunk level builds
that were not published yet. For that reason I did a
checkout-and-build-dependency step in the maven bootstrap phase of my
build. While this was clearly violating the reproducible build
principle, I could live with this trade-off since the features I needed
were additions unlikely to go away. To some extent reproducibility may
be seen as that if you would checkout some project published a few years
ago, it would build without some early failures before javac even kicks
in. I know this is a corner case, but it would suffer from repo contents
(from which a checkout would be done during my build) being moved away.
Regarding Apache policies, there are a few around that might help
finding a decision:
- Apache requires us to run on our own infrastructure for a single
reason: provide resources that will last for ages at the same place.
That is why we would not want to do canonical hosting of projects
externally, such as on GitHub - maybe it shuts down tomorrow? Unlikely,
yes. On the other hand, we have seen such things happen: tr.im URL
shortener was popular by it's time, but then money ran out. Each mailing
list posting containing tr.im URL you will look up in archive render
useless due to the URLs cannot be resolved any more. That's why Apache
even promotes their own URL shortener, http://s.apache.org.
- Dead projects, that is projects with dead communities, go to the Attic
meta project, including move of svn resources. While this has more to do
with having a meta-PMC for keeping oversight even if the owning PMC is
dead, it indeed involves moving of svn resources - AFAIK the only
process where such move happens as a part of an Apache policy. So moving
something to something called "attic" makes me shout out "I'm not dead
yet!" spontaneously :)
So far, I would really tend to go into read-only mode with notices
placed in svn rather than to move things away. If there are good
arguments for the move I have missed so far, I would of course happily
switch my position on that topic.
Just my 0.02$
- René
Am 15.01.14 20:54, schrieb Lukasz Lenart:
> 2014/1/15 Paul Benedict <pb...@apache.org>:
>> The published POMs should all have a link to the SCM URL. We shouldn't move
>> to the attic so those links can stay valid.
>
> Ok, what is wrong if they become invalid? Maybe people start thinking
> about migration :-)
>
>> And what do you mean "cut the wire"? Is that an Apache directive to stop
>> people from going to svn?
>
> I don't know how it is in English - when child is born, connection
> with mother is cut :-) The same here, at some point we must strictly
> say - sorry guys!
>
> It was mentioned as a good practise from other projects which migrated to Git.
>
>
> Regards
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Lukasz Lenart <lu...@apache.org>.
2014/1/15 Paul Benedict <pb...@apache.org>:
> The published POMs should all have a link to the SCM URL. We shouldn't move
> to the attic so those links can stay valid.
Ok, what is wrong if they become invalid? Maybe people start thinking
about migration :-)
> And what do you mean "cut the wire"? Is that an Apache directive to stop
> people from going to svn?
I don't know how it is in English - when child is born, connection
with mother is cut :-) The same here, at some point we must strictly
say - sorry guys!
It was mentioned as a good practise from other projects which migrated to Git.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Paul Benedict <pb...@apache.org>.
The published POMs should all have a link to the SCM URL. We shouldn't move
to the attic so those links can stay valid.
And what do you mean "cut the wire"? Is that an Apache directive to stop
people from going to svn?
On Wed, Jan 15, 2014 at 2:39 AM, Lukasz Lenart <lu...@apache.org>wrote:
> We suppose to cut off the wire - as moving the repos showed that we
> still have a problem with DTDs. And published POMs shouldn't be a
> problem, there are links in ciManagement section only or do I miss
> something?
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2014/1/14 Paul Benedict <pb...@apache.org>:
> > No, please don't move things to the attic. We published POMs and other
> > links to the repository. We should just make it read-only.
> >
> >
> > On Tue, Jan 14, 2014 at 1:23 PM, Johannes Geppert <jo...@gmail.com>
> wrote:
> >
> >> Looks good to me!
> >>
> >> Thanks Łukasz for taking care of this migration.
> >>
> >> Johannes
> >>
> >> #################################################
> >> web: http://www.jgeppert.com
> >> twitter: http://twitter.com/jogep
> >>
> >>
> >> 2014/1/14 Lukasz Lenart <lu...@apache.org>
> >>
> >> > Guys,
> >> > can you review cleanup I have performed?
> >> >
> >> > https://svn.apache.org/repos/asf/struts/
> >> > https://svn.apache.org/repos/asf/struts/attic/
> >> >
> >> > what else I should move to attic as well
> >> >
> >> >
> >> > Regards
> >> > --
> >> > Łukasz
> >> > + 48 606 323 122 http://www.lenart.org.pl/
> >> >
> >> > 2014/1/14 Lukasz Lenart <lu...@apache.org>:
> >> > > I think it isn't needed. I'm going to move everything to 'attic'
> >> > > folder to be backed up and create README about migration
> >> > >
> >> > > 2014/1/14 Paul Benedict <pb...@apache.org>:
> >> > >> Can you request to turn it read only?
> >> > >> On Jan 14, 2014 11:58 AM, "Lukasz Lenart" <lukaszlenart@apache.org
> >
> >> > wrote:
> >> > >>
> >> > >>> Migration to Git is almost done! Please DON'T use Subversion
> anymore!
> >> > >>>
> >> > >>> https://issues.apache.org/jira/browse/INFRA-7174
> >> > >>>
> >> > >>>
> >> > >>> Regards
> >> > >>> --
> >> > >>> Łukasz
> >> > >>> + 48 606 323 122 http://www.lenart.org.pl/
> >> > >>>
> >> > >>> 2014/1/9 Lukasz Lenart <lu...@apache.org>:
> >> > >>> > Time to move forward
> >> > >>> >
> >> > >>> > https://issues.apache.org/jira/browse/INFRA-7174
> >> > >>> >
> >> > >>> > 2013/12/10 Christian Grobmeier <gr...@gmail.com>:
> >> > >>> >> On 10 Dec 2013, at 7:55, Lukasz Lenart wrote:
> >> > >>> >>
> >> > >>> >>> I'm going postpone transition to Git as we must straighten
> site
> >> > >>> >>> building first! Right now it's a real pain in the a.. and it
> >> takes
> >> > >>> >>> ages to update site after release. Not saying about other
> mirror
> >> > >>> >>> problems with this whole SvnPubSub crap :\
> >> > >>> >>
> >> > >>> >>
> >> > >>> >> Oh ok. :-|
> >> > >>> >>
> >> > >>> >> I am a bit undecided on how we approach the website (again).
> >> > >>> >>
> >> > >>> >>
> >> > >>> >>
> >> > >>> >>
> >> > >>> >>>
> >> > >>> >>> Regards
> >> > >>> >>> --
> >> > >>> >>> Łukasz
> >> > >>> >>> + 48 606 323 122 http://www.lenart.org.pl/
> >> > >>> >>>
> >> > >>> >>> 2013/12/6 Dave Newton <da...@gmail.com>:
> >> > >>> >>>>
> >> > >>> >>>> Correct; pull requests are a github thing.
> >> > >>> >>>>
> >> > >>> >>>> And they're nice (usually).
> >> > >>> >>>>
> >> > >>> >>>>
> >> > >>> >>>> On Fri, Dec 6, 2013 at 12:09 PM, Christian Grobmeier
> >> > >>> >>>> <gr...@gmail.com>wrote:
> >> > >>> >>>>
> >> > >>> >>>>> On 6 Dec 2013, at 15:19, Lukasz Lenart wrote:
> >> > >>> >>>>>
> >> > >>> >>>>> 2013/12/6 Christian Grobmeier <gr...@gmail.com>:
> >> > >>> >>>>>>
> >> > >>> >>>>>>
> >> > >>> >>>>>>> On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
> >> > >>> >>>>>>>
> >> > >>> >>>>>>> Do you know if git at Apache supports Pull Requests
> between
> >> > >>> branches?
> >> > >>> >>>>>>>>
> >> > >>> >>>>>>>> I've started working like that some time ago and it's
> >> awesome
> >> > >>> feature
> >> > >>> >>>>>>>> :-)
> >> > >>> >>>>>>>>
> >> > >>> >>>>>>>
> >> > >>> >>>>>>> Honestly I don't know :-)
> >> > >>> >>>>>>>
> >> > >>> >>>>>>> I mean you can merge between branches easily. Is that what
> >> you
> >> > >>> mean?
> >> > >>> >>>>>>>
> >> > >>> >>>>>>
> >> > >>> >>>>>> Not exactly, in GitHub you can prepare a Pull Request
> between
> >> > >>> >>>>>> different branches in the same repo - you don't have to
> fork
> >> the
> >> > >>> repo
> >> > >>> >>>>>> at all. So you'll see the PR on issues list and you can
> >> comment,
> >> > >>> >>>>>> change the code and so on, before merging it to
> mater/develop.
> >> > >>> >>>>>>
> >> > >>> >>>>>> But I think it's pure GitHub functionality not really
> related
> >> > to git
> >> > >>> >>>>>> itself.
> >> > >>> >>>>>>
> >> > >>> >>>>>
> >> > >>> >>>>> I don't know for sure, but I agree, its most likely a github
> >> > feature.
> >> > >>> >>>>> I think something like gitlabhq might be able to do the
> same:
> >> > >>> >>>>> https://github.com/gitlabhq/gitlabhq
> >> > >>> >>>>> But i have not heard if this is going to live at ASF infra
> >> > >>> >>>>>
> >> > >>> >>>>>
> >> > >>> >>>>>> Regards
> >> > >>> >>>>>> --
> >> > >>> >>>>>> Łukasz
> >> > >>> >>>>>> + 48 606 323 122 http://www.lenart.org.pl/
> >> > >>> >>>>>>
> >> > >>> >>>>>>
> >> > >>>
> ---------------------------------------------------------------------
> >> > >>> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> > >>> >>>>>> For additional commands, e-mail:
> dev-help@struts.apache.org
> >> > >>> >>>>>>
> >> > >>> >>>>>
> >> > >>> >>>>>
> >> > >>> >>>>> ---
> >> > >>> >>>>> http://www.grobmeier.de
> >> > >>> >>>>> @grobmeier
> >> > >>> >>>>> GPG: 0xA5CC90DB
> >> > >>> >>>>>
> >> > >>> >>>>>
> >> > ---------------------------------------------------------------------
> >> > >>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> > >>> >>>>> For additional commands, e-mail: dev-help@struts.apache.org
> >> > >>> >>>>>
> >> > >>> >>>>>
> >> > >>> >>>>
> >> > >>> >>>>
> >> > >>> >>>> --
> >> > >>> >>>> e: davelnewton@gmail.com
> >> > >>> >>>> m: 908-380-8699
> >> > >>> >>>> s: davelnewton_skype
> >> > >>> >>>> t: @dave_newton <https://twitter.com/dave_newton>
> >> > >>> >>>> b: Bucky Bits <http://buckybits.blogspot.com/>
> >> > >>> >>>> g: davelnewton <https://github.com/davelnewton>
> >> > >>> >>>> so: Dave Newton <
> >> > http://stackoverflow.com/users/438992/dave-newton>
> >> > >>> >>>
> >> > >>> >>>
> >> > >>> >>>
> >> > ---------------------------------------------------------------------
> >> > >>> >>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> > >>> >>> For additional commands, e-mail: dev-help@struts.apache.org
> >> > >>> >>
> >> > >>> >>
> >> > >>> >>
> >> > >>> >> ---
> >> > >>> >> http://www.grobmeier.de
> >> > >>> >> @grobmeier
> >> > >>> >> GPG: 0xA5CC90DB
> >> > >>> >>
> >> > >>> >>
> >> > ---------------------------------------------------------------------
> >> > >>> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> > >>> >> For additional commands, e-mail: dev-help@struts.apache.org
> >> > >>> >>
> >> > >>>
> >> > >>>
> ---------------------------------------------------------------------
> >> > >>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> > >>> For additional commands, e-mail: dev-help@struts.apache.org
> >> > >>>
> >> > >>>
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> > For additional commands, e-mail: dev-help@struts.apache.org
> >> >
> >> >
> >>
> >
> >
> >
> > --
> > Cheers,
> > Paul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
Cheers,
Paul
Re: Svn to Git migration
Posted by Lukasz Lenart <lu...@apache.org>.
We suppose to cut off the wire - as moving the repos showed that we
still have a problem with DTDs. And published POMs shouldn't be a
problem, there are links in ciManagement section only or do I miss
something?
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2014/1/14 Paul Benedict <pb...@apache.org>:
> No, please don't move things to the attic. We published POMs and other
> links to the repository. We should just make it read-only.
>
>
> On Tue, Jan 14, 2014 at 1:23 PM, Johannes Geppert <jo...@gmail.com> wrote:
>
>> Looks good to me!
>>
>> Thanks Łukasz for taking care of this migration.
>>
>> Johannes
>>
>> #################################################
>> web: http://www.jgeppert.com
>> twitter: http://twitter.com/jogep
>>
>>
>> 2014/1/14 Lukasz Lenart <lu...@apache.org>
>>
>> > Guys,
>> > can you review cleanup I have performed?
>> >
>> > https://svn.apache.org/repos/asf/struts/
>> > https://svn.apache.org/repos/asf/struts/attic/
>> >
>> > what else I should move to attic as well
>> >
>> >
>> > Regards
>> > --
>> > Łukasz
>> > + 48 606 323 122 http://www.lenart.org.pl/
>> >
>> > 2014/1/14 Lukasz Lenart <lu...@apache.org>:
>> > > I think it isn't needed. I'm going to move everything to 'attic'
>> > > folder to be backed up and create README about migration
>> > >
>> > > 2014/1/14 Paul Benedict <pb...@apache.org>:
>> > >> Can you request to turn it read only?
>> > >> On Jan 14, 2014 11:58 AM, "Lukasz Lenart" <lu...@apache.org>
>> > wrote:
>> > >>
>> > >>> Migration to Git is almost done! Please DON'T use Subversion anymore!
>> > >>>
>> > >>> https://issues.apache.org/jira/browse/INFRA-7174
>> > >>>
>> > >>>
>> > >>> Regards
>> > >>> --
>> > >>> Łukasz
>> > >>> + 48 606 323 122 http://www.lenart.org.pl/
>> > >>>
>> > >>> 2014/1/9 Lukasz Lenart <lu...@apache.org>:
>> > >>> > Time to move forward
>> > >>> >
>> > >>> > https://issues.apache.org/jira/browse/INFRA-7174
>> > >>> >
>> > >>> > 2013/12/10 Christian Grobmeier <gr...@gmail.com>:
>> > >>> >> On 10 Dec 2013, at 7:55, Lukasz Lenart wrote:
>> > >>> >>
>> > >>> >>> I'm going postpone transition to Git as we must straighten site
>> > >>> >>> building first! Right now it's a real pain in the a.. and it
>> takes
>> > >>> >>> ages to update site after release. Not saying about other mirror
>> > >>> >>> problems with this whole SvnPubSub crap :\
>> > >>> >>
>> > >>> >>
>> > >>> >> Oh ok. :-|
>> > >>> >>
>> > >>> >> I am a bit undecided on how we approach the website (again).
>> > >>> >>
>> > >>> >>
>> > >>> >>
>> > >>> >>
>> > >>> >>>
>> > >>> >>> Regards
>> > >>> >>> --
>> > >>> >>> Łukasz
>> > >>> >>> + 48 606 323 122 http://www.lenart.org.pl/
>> > >>> >>>
>> > >>> >>> 2013/12/6 Dave Newton <da...@gmail.com>:
>> > >>> >>>>
>> > >>> >>>> Correct; pull requests are a github thing.
>> > >>> >>>>
>> > >>> >>>> And they're nice (usually).
>> > >>> >>>>
>> > >>> >>>>
>> > >>> >>>> On Fri, Dec 6, 2013 at 12:09 PM, Christian Grobmeier
>> > >>> >>>> <gr...@gmail.com>wrote:
>> > >>> >>>>
>> > >>> >>>>> On 6 Dec 2013, at 15:19, Lukasz Lenart wrote:
>> > >>> >>>>>
>> > >>> >>>>> 2013/12/6 Christian Grobmeier <gr...@gmail.com>:
>> > >>> >>>>>>
>> > >>> >>>>>>
>> > >>> >>>>>>> On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
>> > >>> >>>>>>>
>> > >>> >>>>>>> Do you know if git at Apache supports Pull Requests between
>> > >>> branches?
>> > >>> >>>>>>>>
>> > >>> >>>>>>>> I've started working like that some time ago and it's
>> awesome
>> > >>> feature
>> > >>> >>>>>>>> :-)
>> > >>> >>>>>>>>
>> > >>> >>>>>>>
>> > >>> >>>>>>> Honestly I don't know :-)
>> > >>> >>>>>>>
>> > >>> >>>>>>> I mean you can merge between branches easily. Is that what
>> you
>> > >>> mean?
>> > >>> >>>>>>>
>> > >>> >>>>>>
>> > >>> >>>>>> Not exactly, in GitHub you can prepare a Pull Request between
>> > >>> >>>>>> different branches in the same repo - you don't have to fork
>> the
>> > >>> repo
>> > >>> >>>>>> at all. So you'll see the PR on issues list and you can
>> comment,
>> > >>> >>>>>> change the code and so on, before merging it to mater/develop.
>> > >>> >>>>>>
>> > >>> >>>>>> But I think it's pure GitHub functionality not really related
>> > to git
>> > >>> >>>>>> itself.
>> > >>> >>>>>>
>> > >>> >>>>>
>> > >>> >>>>> I don't know for sure, but I agree, its most likely a github
>> > feature.
>> > >>> >>>>> I think something like gitlabhq might be able to do the same:
>> > >>> >>>>> https://github.com/gitlabhq/gitlabhq
>> > >>> >>>>> But i have not heard if this is going to live at ASF infra
>> > >>> >>>>>
>> > >>> >>>>>
>> > >>> >>>>>> Regards
>> > >>> >>>>>> --
>> > >>> >>>>>> Łukasz
>> > >>> >>>>>> + 48 606 323 122 http://www.lenart.org.pl/
>> > >>> >>>>>>
>> > >>> >>>>>>
>> > >>> ---------------------------------------------------------------------
>> > >>> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> > >>> >>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>> > >>> >>>>>>
>> > >>> >>>>>
>> > >>> >>>>>
>> > >>> >>>>> ---
>> > >>> >>>>> http://www.grobmeier.de
>> > >>> >>>>> @grobmeier
>> > >>> >>>>> GPG: 0xA5CC90DB
>> > >>> >>>>>
>> > >>> >>>>>
>> > ---------------------------------------------------------------------
>> > >>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> > >>> >>>>> For additional commands, e-mail: dev-help@struts.apache.org
>> > >>> >>>>>
>> > >>> >>>>>
>> > >>> >>>>
>> > >>> >>>>
>> > >>> >>>> --
>> > >>> >>>> e: davelnewton@gmail.com
>> > >>> >>>> m: 908-380-8699
>> > >>> >>>> s: davelnewton_skype
>> > >>> >>>> t: @dave_newton <https://twitter.com/dave_newton>
>> > >>> >>>> b: Bucky Bits <http://buckybits.blogspot.com/>
>> > >>> >>>> g: davelnewton <https://github.com/davelnewton>
>> > >>> >>>> so: Dave Newton <
>> > http://stackoverflow.com/users/438992/dave-newton>
>> > >>> >>>
>> > >>> >>>
>> > >>> >>>
>> > ---------------------------------------------------------------------
>> > >>> >>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> > >>> >>> For additional commands, e-mail: dev-help@struts.apache.org
>> > >>> >>
>> > >>> >>
>> > >>> >>
>> > >>> >> ---
>> > >>> >> http://www.grobmeier.de
>> > >>> >> @grobmeier
>> > >>> >> GPG: 0xA5CC90DB
>> > >>> >>
>> > >>> >>
>> > ---------------------------------------------------------------------
>> > >>> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> > >>> >> For additional commands, e-mail: dev-help@struts.apache.org
>> > >>> >>
>> > >>>
>> > >>> ---------------------------------------------------------------------
>> > >>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> > >>> For additional commands, e-mail: dev-help@struts.apache.org
>> > >>>
>> > >>>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> > For additional commands, e-mail: dev-help@struts.apache.org
>> >
>> >
>>
>
>
>
> --
> Cheers,
> Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Paul Benedict <pb...@apache.org>.
No, please don't move things to the attic. We published POMs and other
links to the repository. We should just make it read-only.
On Tue, Jan 14, 2014 at 1:23 PM, Johannes Geppert <jo...@gmail.com> wrote:
> Looks good to me!
>
> Thanks Łukasz for taking care of this migration.
>
> Johannes
>
> #################################################
> web: http://www.jgeppert.com
> twitter: http://twitter.com/jogep
>
>
> 2014/1/14 Lukasz Lenart <lu...@apache.org>
>
> > Guys,
> > can you review cleanup I have performed?
> >
> > https://svn.apache.org/repos/asf/struts/
> > https://svn.apache.org/repos/asf/struts/attic/
> >
> > what else I should move to attic as well
> >
> >
> > Regards
> > --
> > Łukasz
> > + 48 606 323 122 http://www.lenart.org.pl/
> >
> > 2014/1/14 Lukasz Lenart <lu...@apache.org>:
> > > I think it isn't needed. I'm going to move everything to 'attic'
> > > folder to be backed up and create README about migration
> > >
> > > 2014/1/14 Paul Benedict <pb...@apache.org>:
> > >> Can you request to turn it read only?
> > >> On Jan 14, 2014 11:58 AM, "Lukasz Lenart" <lu...@apache.org>
> > wrote:
> > >>
> > >>> Migration to Git is almost done! Please DON'T use Subversion anymore!
> > >>>
> > >>> https://issues.apache.org/jira/browse/INFRA-7174
> > >>>
> > >>>
> > >>> Regards
> > >>> --
> > >>> Łukasz
> > >>> + 48 606 323 122 http://www.lenart.org.pl/
> > >>>
> > >>> 2014/1/9 Lukasz Lenart <lu...@apache.org>:
> > >>> > Time to move forward
> > >>> >
> > >>> > https://issues.apache.org/jira/browse/INFRA-7174
> > >>> >
> > >>> > 2013/12/10 Christian Grobmeier <gr...@gmail.com>:
> > >>> >> On 10 Dec 2013, at 7:55, Lukasz Lenart wrote:
> > >>> >>
> > >>> >>> I'm going postpone transition to Git as we must straighten site
> > >>> >>> building first! Right now it's a real pain in the a.. and it
> takes
> > >>> >>> ages to update site after release. Not saying about other mirror
> > >>> >>> problems with this whole SvnPubSub crap :\
> > >>> >>
> > >>> >>
> > >>> >> Oh ok. :-|
> > >>> >>
> > >>> >> I am a bit undecided on how we approach the website (again).
> > >>> >>
> > >>> >>
> > >>> >>
> > >>> >>
> > >>> >>>
> > >>> >>> Regards
> > >>> >>> --
> > >>> >>> Łukasz
> > >>> >>> + 48 606 323 122 http://www.lenart.org.pl/
> > >>> >>>
> > >>> >>> 2013/12/6 Dave Newton <da...@gmail.com>:
> > >>> >>>>
> > >>> >>>> Correct; pull requests are a github thing.
> > >>> >>>>
> > >>> >>>> And they're nice (usually).
> > >>> >>>>
> > >>> >>>>
> > >>> >>>> On Fri, Dec 6, 2013 at 12:09 PM, Christian Grobmeier
> > >>> >>>> <gr...@gmail.com>wrote:
> > >>> >>>>
> > >>> >>>>> On 6 Dec 2013, at 15:19, Lukasz Lenart wrote:
> > >>> >>>>>
> > >>> >>>>> 2013/12/6 Christian Grobmeier <gr...@gmail.com>:
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> >>>>>>> On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
> > >>> >>>>>>>
> > >>> >>>>>>> Do you know if git at Apache supports Pull Requests between
> > >>> branches?
> > >>> >>>>>>>>
> > >>> >>>>>>>> I've started working like that some time ago and it's
> awesome
> > >>> feature
> > >>> >>>>>>>> :-)
> > >>> >>>>>>>>
> > >>> >>>>>>>
> > >>> >>>>>>> Honestly I don't know :-)
> > >>> >>>>>>>
> > >>> >>>>>>> I mean you can merge between branches easily. Is that what
> you
> > >>> mean?
> > >>> >>>>>>>
> > >>> >>>>>>
> > >>> >>>>>> Not exactly, in GitHub you can prepare a Pull Request between
> > >>> >>>>>> different branches in the same repo - you don't have to fork
> the
> > >>> repo
> > >>> >>>>>> at all. So you'll see the PR on issues list and you can
> comment,
> > >>> >>>>>> change the code and so on, before merging it to mater/develop.
> > >>> >>>>>>
> > >>> >>>>>> But I think it's pure GitHub functionality not really related
> > to git
> > >>> >>>>>> itself.
> > >>> >>>>>>
> > >>> >>>>>
> > >>> >>>>> I don't know for sure, but I agree, its most likely a github
> > feature.
> > >>> >>>>> I think something like gitlabhq might be able to do the same:
> > >>> >>>>> https://github.com/gitlabhq/gitlabhq
> > >>> >>>>> But i have not heard if this is going to live at ASF infra
> > >>> >>>>>
> > >>> >>>>>
> > >>> >>>>>> Regards
> > >>> >>>>>> --
> > >>> >>>>>> Łukasz
> > >>> >>>>>> + 48 606 323 122 http://www.lenart.org.pl/
> > >>> >>>>>>
> > >>> >>>>>>
> > >>> ---------------------------------------------------------------------
> > >>> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > >>> >>>>>> For additional commands, e-mail: dev-help@struts.apache.org
> > >>> >>>>>>
> > >>> >>>>>
> > >>> >>>>>
> > >>> >>>>> ---
> > >>> >>>>> http://www.grobmeier.de
> > >>> >>>>> @grobmeier
> > >>> >>>>> GPG: 0xA5CC90DB
> > >>> >>>>>
> > >>> >>>>>
> > ---------------------------------------------------------------------
> > >>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > >>> >>>>> For additional commands, e-mail: dev-help@struts.apache.org
> > >>> >>>>>
> > >>> >>>>>
> > >>> >>>>
> > >>> >>>>
> > >>> >>>> --
> > >>> >>>> e: davelnewton@gmail.com
> > >>> >>>> m: 908-380-8699
> > >>> >>>> s: davelnewton_skype
> > >>> >>>> t: @dave_newton <https://twitter.com/dave_newton>
> > >>> >>>> b: Bucky Bits <http://buckybits.blogspot.com/>
> > >>> >>>> g: davelnewton <https://github.com/davelnewton>
> > >>> >>>> so: Dave Newton <
> > http://stackoverflow.com/users/438992/dave-newton>
> > >>> >>>
> > >>> >>>
> > >>> >>>
> > ---------------------------------------------------------------------
> > >>> >>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > >>> >>> For additional commands, e-mail: dev-help@struts.apache.org
> > >>> >>
> > >>> >>
> > >>> >>
> > >>> >> ---
> > >>> >> http://www.grobmeier.de
> > >>> >> @grobmeier
> > >>> >> GPG: 0xA5CC90DB
> > >>> >>
> > >>> >>
> > ---------------------------------------------------------------------
> > >>> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > >>> >> For additional commands, e-mail: dev-help@struts.apache.org
> > >>> >>
> > >>>
> > >>> ---------------------------------------------------------------------
> > >>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > >>> For additional commands, e-mail: dev-help@struts.apache.org
> > >>>
> > >>>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
--
Cheers,
Paul
Re: Svn to Git migration
Posted by Johannes Geppert <jo...@gmail.com>.
Looks good to me!
Thanks Łukasz for taking care of this migration.
Johannes
#################################################
web: http://www.jgeppert.com
twitter: http://twitter.com/jogep
2014/1/14 Lukasz Lenart <lu...@apache.org>
> Guys,
> can you review cleanup I have performed?
>
> https://svn.apache.org/repos/asf/struts/
> https://svn.apache.org/repos/asf/struts/attic/
>
> what else I should move to attic as well
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2014/1/14 Lukasz Lenart <lu...@apache.org>:
> > I think it isn't needed. I'm going to move everything to 'attic'
> > folder to be backed up and create README about migration
> >
> > 2014/1/14 Paul Benedict <pb...@apache.org>:
> >> Can you request to turn it read only?
> >> On Jan 14, 2014 11:58 AM, "Lukasz Lenart" <lu...@apache.org>
> wrote:
> >>
> >>> Migration to Git is almost done! Please DON'T use Subversion anymore!
> >>>
> >>> https://issues.apache.org/jira/browse/INFRA-7174
> >>>
> >>>
> >>> Regards
> >>> --
> >>> Łukasz
> >>> + 48 606 323 122 http://www.lenart.org.pl/
> >>>
> >>> 2014/1/9 Lukasz Lenart <lu...@apache.org>:
> >>> > Time to move forward
> >>> >
> >>> > https://issues.apache.org/jira/browse/INFRA-7174
> >>> >
> >>> > 2013/12/10 Christian Grobmeier <gr...@gmail.com>:
> >>> >> On 10 Dec 2013, at 7:55, Lukasz Lenart wrote:
> >>> >>
> >>> >>> I'm going postpone transition to Git as we must straighten site
> >>> >>> building first! Right now it's a real pain in the a.. and it takes
> >>> >>> ages to update site after release. Not saying about other mirror
> >>> >>> problems with this whole SvnPubSub crap :\
> >>> >>
> >>> >>
> >>> >> Oh ok. :-|
> >>> >>
> >>> >> I am a bit undecided on how we approach the website (again).
> >>> >>
> >>> >>
> >>> >>
> >>> >>
> >>> >>>
> >>> >>> Regards
> >>> >>> --
> >>> >>> Łukasz
> >>> >>> + 48 606 323 122 http://www.lenart.org.pl/
> >>> >>>
> >>> >>> 2013/12/6 Dave Newton <da...@gmail.com>:
> >>> >>>>
> >>> >>>> Correct; pull requests are a github thing.
> >>> >>>>
> >>> >>>> And they're nice (usually).
> >>> >>>>
> >>> >>>>
> >>> >>>> On Fri, Dec 6, 2013 at 12:09 PM, Christian Grobmeier
> >>> >>>> <gr...@gmail.com>wrote:
> >>> >>>>
> >>> >>>>> On 6 Dec 2013, at 15:19, Lukasz Lenart wrote:
> >>> >>>>>
> >>> >>>>> 2013/12/6 Christian Grobmeier <gr...@gmail.com>:
> >>> >>>>>>
> >>> >>>>>>
> >>> >>>>>>> On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
> >>> >>>>>>>
> >>> >>>>>>> Do you know if git at Apache supports Pull Requests between
> >>> branches?
> >>> >>>>>>>>
> >>> >>>>>>>> I've started working like that some time ago and it's awesome
> >>> feature
> >>> >>>>>>>> :-)
> >>> >>>>>>>>
> >>> >>>>>>>
> >>> >>>>>>> Honestly I don't know :-)
> >>> >>>>>>>
> >>> >>>>>>> I mean you can merge between branches easily. Is that what you
> >>> mean?
> >>> >>>>>>>
> >>> >>>>>>
> >>> >>>>>> Not exactly, in GitHub you can prepare a Pull Request between
> >>> >>>>>> different branches in the same repo - you don't have to fork the
> >>> repo
> >>> >>>>>> at all. So you'll see the PR on issues list and you can comment,
> >>> >>>>>> change the code and so on, before merging it to mater/develop.
> >>> >>>>>>
> >>> >>>>>> But I think it's pure GitHub functionality not really related
> to git
> >>> >>>>>> itself.
> >>> >>>>>>
> >>> >>>>>
> >>> >>>>> I don't know for sure, but I agree, its most likely a github
> feature.
> >>> >>>>> I think something like gitlabhq might be able to do the same:
> >>> >>>>> https://github.com/gitlabhq/gitlabhq
> >>> >>>>> But i have not heard if this is going to live at ASF infra
> >>> >>>>>
> >>> >>>>>
> >>> >>>>>> Regards
> >>> >>>>>> --
> >>> >>>>>> Łukasz
> >>> >>>>>> + 48 606 323 122 http://www.lenart.org.pl/
> >>> >>>>>>
> >>> >>>>>>
> >>> ---------------------------------------------------------------------
> >>> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >>> >>>>>> For additional commands, e-mail: dev-help@struts.apache.org
> >>> >>>>>>
> >>> >>>>>
> >>> >>>>>
> >>> >>>>> ---
> >>> >>>>> http://www.grobmeier.de
> >>> >>>>> @grobmeier
> >>> >>>>> GPG: 0xA5CC90DB
> >>> >>>>>
> >>> >>>>>
> ---------------------------------------------------------------------
> >>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >>> >>>>> For additional commands, e-mail: dev-help@struts.apache.org
> >>> >>>>>
> >>> >>>>>
> >>> >>>>
> >>> >>>>
> >>> >>>> --
> >>> >>>> e: davelnewton@gmail.com
> >>> >>>> m: 908-380-8699
> >>> >>>> s: davelnewton_skype
> >>> >>>> t: @dave_newton <https://twitter.com/dave_newton>
> >>> >>>> b: Bucky Bits <http://buckybits.blogspot.com/>
> >>> >>>> g: davelnewton <https://github.com/davelnewton>
> >>> >>>> so: Dave Newton <
> http://stackoverflow.com/users/438992/dave-newton>
> >>> >>>
> >>> >>>
> >>> >>>
> ---------------------------------------------------------------------
> >>> >>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >>> >>> For additional commands, e-mail: dev-help@struts.apache.org
> >>> >>
> >>> >>
> >>> >>
> >>> >> ---
> >>> >> http://www.grobmeier.de
> >>> >> @grobmeier
> >>> >> GPG: 0xA5CC90DB
> >>> >>
> >>> >>
> ---------------------------------------------------------------------
> >>> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >>> >> For additional commands, e-mail: dev-help@struts.apache.org
> >>> >>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >>> For additional commands, e-mail: dev-help@struts.apache.org
> >>>
> >>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: Svn to Git migration
Posted by Lukasz Lenart <lu...@apache.org>.
Guys,
can you review cleanup I have performed?
https://svn.apache.org/repos/asf/struts/
https://svn.apache.org/repos/asf/struts/attic/
what else I should move to attic as well
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2014/1/14 Lukasz Lenart <lu...@apache.org>:
> I think it isn't needed. I'm going to move everything to 'attic'
> folder to be backed up and create README about migration
>
> 2014/1/14 Paul Benedict <pb...@apache.org>:
>> Can you request to turn it read only?
>> On Jan 14, 2014 11:58 AM, "Lukasz Lenart" <lu...@apache.org> wrote:
>>
>>> Migration to Git is almost done! Please DON'T use Subversion anymore!
>>>
>>> https://issues.apache.org/jira/browse/INFRA-7174
>>>
>>>
>>> Regards
>>> --
>>> Łukasz
>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>
>>> 2014/1/9 Lukasz Lenart <lu...@apache.org>:
>>> > Time to move forward
>>> >
>>> > https://issues.apache.org/jira/browse/INFRA-7174
>>> >
>>> > 2013/12/10 Christian Grobmeier <gr...@gmail.com>:
>>> >> On 10 Dec 2013, at 7:55, Lukasz Lenart wrote:
>>> >>
>>> >>> I'm going postpone transition to Git as we must straighten site
>>> >>> building first! Right now it's a real pain in the a.. and it takes
>>> >>> ages to update site after release. Not saying about other mirror
>>> >>> problems with this whole SvnPubSub crap :\
>>> >>
>>> >>
>>> >> Oh ok. :-|
>>> >>
>>> >> I am a bit undecided on how we approach the website (again).
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>>
>>> >>> Regards
>>> >>> --
>>> >>> Łukasz
>>> >>> + 48 606 323 122 http://www.lenart.org.pl/
>>> >>>
>>> >>> 2013/12/6 Dave Newton <da...@gmail.com>:
>>> >>>>
>>> >>>> Correct; pull requests are a github thing.
>>> >>>>
>>> >>>> And they're nice (usually).
>>> >>>>
>>> >>>>
>>> >>>> On Fri, Dec 6, 2013 at 12:09 PM, Christian Grobmeier
>>> >>>> <gr...@gmail.com>wrote:
>>> >>>>
>>> >>>>> On 6 Dec 2013, at 15:19, Lukasz Lenart wrote:
>>> >>>>>
>>> >>>>> 2013/12/6 Christian Grobmeier <gr...@gmail.com>:
>>> >>>>>>
>>> >>>>>>
>>> >>>>>>> On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
>>> >>>>>>>
>>> >>>>>>> Do you know if git at Apache supports Pull Requests between
>>> branches?
>>> >>>>>>>>
>>> >>>>>>>> I've started working like that some time ago and it's awesome
>>> feature
>>> >>>>>>>> :-)
>>> >>>>>>>>
>>> >>>>>>>
>>> >>>>>>> Honestly I don't know :-)
>>> >>>>>>>
>>> >>>>>>> I mean you can merge between branches easily. Is that what you
>>> mean?
>>> >>>>>>>
>>> >>>>>>
>>> >>>>>> Not exactly, in GitHub you can prepare a Pull Request between
>>> >>>>>> different branches in the same repo - you don't have to fork the
>>> repo
>>> >>>>>> at all. So you'll see the PR on issues list and you can comment,
>>> >>>>>> change the code and so on, before merging it to mater/develop.
>>> >>>>>>
>>> >>>>>> But I think it's pure GitHub functionality not really related to git
>>> >>>>>> itself.
>>> >>>>>>
>>> >>>>>
>>> >>>>> I don't know for sure, but I agree, its most likely a github feature.
>>> >>>>> I think something like gitlabhq might be able to do the same:
>>> >>>>> https://github.com/gitlabhq/gitlabhq
>>> >>>>> But i have not heard if this is going to live at ASF infra
>>> >>>>>
>>> >>>>>
>>> >>>>>> Regards
>>> >>>>>> --
>>> >>>>>> Łukasz
>>> >>>>>> + 48 606 323 122 http://www.lenart.org.pl/
>>> >>>>>>
>>> >>>>>>
>>> ---------------------------------------------------------------------
>>> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> >>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>> >>>>>>
>>> >>>>>
>>> >>>>>
>>> >>>>> ---
>>> >>>>> http://www.grobmeier.de
>>> >>>>> @grobmeier
>>> >>>>> GPG: 0xA5CC90DB
>>> >>>>>
>>> >>>>> ---------------------------------------------------------------------
>>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> >>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>> >>>>>
>>> >>>>>
>>> >>>>
>>> >>>>
>>> >>>> --
>>> >>>> e: davelnewton@gmail.com
>>> >>>> m: 908-380-8699
>>> >>>> s: davelnewton_skype
>>> >>>> t: @dave_newton <https://twitter.com/dave_newton>
>>> >>>> b: Bucky Bits <http://buckybits.blogspot.com/>
>>> >>>> g: davelnewton <https://github.com/davelnewton>
>>> >>>> so: Dave Newton <http://stackoverflow.com/users/438992/dave-newton>
>>> >>>
>>> >>>
>>> >>> ---------------------------------------------------------------------
>>> >>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> >>> For additional commands, e-mail: dev-help@struts.apache.org
>>> >>
>>> >>
>>> >>
>>> >> ---
>>> >> http://www.grobmeier.de
>>> >> @grobmeier
>>> >> GPG: 0xA5CC90DB
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> >> For additional commands, e-mail: dev-help@struts.apache.org
>>> >>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Lukasz Lenart <lu...@apache.org>.
I think it isn't needed. I'm going to move everything to 'attic'
folder to be backed up and create README about migration
2014/1/14 Paul Benedict <pb...@apache.org>:
> Can you request to turn it read only?
> On Jan 14, 2014 11:58 AM, "Lukasz Lenart" <lu...@apache.org> wrote:
>
>> Migration to Git is almost done! Please DON'T use Subversion anymore!
>>
>> https://issues.apache.org/jira/browse/INFRA-7174
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>>
>> 2014/1/9 Lukasz Lenart <lu...@apache.org>:
>> > Time to move forward
>> >
>> > https://issues.apache.org/jira/browse/INFRA-7174
>> >
>> > 2013/12/10 Christian Grobmeier <gr...@gmail.com>:
>> >> On 10 Dec 2013, at 7:55, Lukasz Lenart wrote:
>> >>
>> >>> I'm going postpone transition to Git as we must straighten site
>> >>> building first! Right now it's a real pain in the a.. and it takes
>> >>> ages to update site after release. Not saying about other mirror
>> >>> problems with this whole SvnPubSub crap :\
>> >>
>> >>
>> >> Oh ok. :-|
>> >>
>> >> I am a bit undecided on how we approach the website (again).
>> >>
>> >>
>> >>
>> >>
>> >>>
>> >>> Regards
>> >>> --
>> >>> Łukasz
>> >>> + 48 606 323 122 http://www.lenart.org.pl/
>> >>>
>> >>> 2013/12/6 Dave Newton <da...@gmail.com>:
>> >>>>
>> >>>> Correct; pull requests are a github thing.
>> >>>>
>> >>>> And they're nice (usually).
>> >>>>
>> >>>>
>> >>>> On Fri, Dec 6, 2013 at 12:09 PM, Christian Grobmeier
>> >>>> <gr...@gmail.com>wrote:
>> >>>>
>> >>>>> On 6 Dec 2013, at 15:19, Lukasz Lenart wrote:
>> >>>>>
>> >>>>> 2013/12/6 Christian Grobmeier <gr...@gmail.com>:
>> >>>>>>
>> >>>>>>
>> >>>>>>> On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
>> >>>>>>>
>> >>>>>>> Do you know if git at Apache supports Pull Requests between
>> branches?
>> >>>>>>>>
>> >>>>>>>> I've started working like that some time ago and it's awesome
>> feature
>> >>>>>>>> :-)
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>> Honestly I don't know :-)
>> >>>>>>>
>> >>>>>>> I mean you can merge between branches easily. Is that what you
>> mean?
>> >>>>>>>
>> >>>>>>
>> >>>>>> Not exactly, in GitHub you can prepare a Pull Request between
>> >>>>>> different branches in the same repo - you don't have to fork the
>> repo
>> >>>>>> at all. So you'll see the PR on issues list and you can comment,
>> >>>>>> change the code and so on, before merging it to mater/develop.
>> >>>>>>
>> >>>>>> But I think it's pure GitHub functionality not really related to git
>> >>>>>> itself.
>> >>>>>>
>> >>>>>
>> >>>>> I don't know for sure, but I agree, its most likely a github feature.
>> >>>>> I think something like gitlabhq might be able to do the same:
>> >>>>> https://github.com/gitlabhq/gitlabhq
>> >>>>> But i have not heard if this is going to live at ASF infra
>> >>>>>
>> >>>>>
>> >>>>>> Regards
>> >>>>>> --
>> >>>>>> Łukasz
>> >>>>>> + 48 606 323 122 http://www.lenart.org.pl/
>> >>>>>>
>> >>>>>>
>> ---------------------------------------------------------------------
>> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> >>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>> ---
>> >>>>> http://www.grobmeier.de
>> >>>>> @grobmeier
>> >>>>> GPG: 0xA5CC90DB
>> >>>>>
>> >>>>> ---------------------------------------------------------------------
>> >>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> >>>>> For additional commands, e-mail: dev-help@struts.apache.org
>> >>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> e: davelnewton@gmail.com
>> >>>> m: 908-380-8699
>> >>>> s: davelnewton_skype
>> >>>> t: @dave_newton <https://twitter.com/dave_newton>
>> >>>> b: Bucky Bits <http://buckybits.blogspot.com/>
>> >>>> g: davelnewton <https://github.com/davelnewton>
>> >>>> so: Dave Newton <http://stackoverflow.com/users/438992/dave-newton>
>> >>>
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> >>> For additional commands, e-mail: dev-help@struts.apache.org
>> >>
>> >>
>> >>
>> >> ---
>> >> http://www.grobmeier.de
>> >> @grobmeier
>> >> GPG: 0xA5CC90DB
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> >> For additional commands, e-mail: dev-help@struts.apache.org
>> >>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Paul Benedict <pb...@apache.org>.
Can you request to turn it read only?
On Jan 14, 2014 11:58 AM, "Lukasz Lenart" <lu...@apache.org> wrote:
> Migration to Git is almost done! Please DON'T use Subversion anymore!
>
> https://issues.apache.org/jira/browse/INFRA-7174
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2014/1/9 Lukasz Lenart <lu...@apache.org>:
> > Time to move forward
> >
> > https://issues.apache.org/jira/browse/INFRA-7174
> >
> > 2013/12/10 Christian Grobmeier <gr...@gmail.com>:
> >> On 10 Dec 2013, at 7:55, Lukasz Lenart wrote:
> >>
> >>> I'm going postpone transition to Git as we must straighten site
> >>> building first! Right now it's a real pain in the a.. and it takes
> >>> ages to update site after release. Not saying about other mirror
> >>> problems with this whole SvnPubSub crap :\
> >>
> >>
> >> Oh ok. :-|
> >>
> >> I am a bit undecided on how we approach the website (again).
> >>
> >>
> >>
> >>
> >>>
> >>> Regards
> >>> --
> >>> Łukasz
> >>> + 48 606 323 122 http://www.lenart.org.pl/
> >>>
> >>> 2013/12/6 Dave Newton <da...@gmail.com>:
> >>>>
> >>>> Correct; pull requests are a github thing.
> >>>>
> >>>> And they're nice (usually).
> >>>>
> >>>>
> >>>> On Fri, Dec 6, 2013 at 12:09 PM, Christian Grobmeier
> >>>> <gr...@gmail.com>wrote:
> >>>>
> >>>>> On 6 Dec 2013, at 15:19, Lukasz Lenart wrote:
> >>>>>
> >>>>> 2013/12/6 Christian Grobmeier <gr...@gmail.com>:
> >>>>>>
> >>>>>>
> >>>>>>> On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
> >>>>>>>
> >>>>>>> Do you know if git at Apache supports Pull Requests between
> branches?
> >>>>>>>>
> >>>>>>>> I've started working like that some time ago and it's awesome
> feature
> >>>>>>>> :-)
> >>>>>>>>
> >>>>>>>
> >>>>>>> Honestly I don't know :-)
> >>>>>>>
> >>>>>>> I mean you can merge between branches easily. Is that what you
> mean?
> >>>>>>>
> >>>>>>
> >>>>>> Not exactly, in GitHub you can prepare a Pull Request between
> >>>>>> different branches in the same repo - you don't have to fork the
> repo
> >>>>>> at all. So you'll see the PR on issues list and you can comment,
> >>>>>> change the code and so on, before merging it to mater/develop.
> >>>>>>
> >>>>>> But I think it's pure GitHub functionality not really related to git
> >>>>>> itself.
> >>>>>>
> >>>>>
> >>>>> I don't know for sure, but I agree, its most likely a github feature.
> >>>>> I think something like gitlabhq might be able to do the same:
> >>>>> https://github.com/gitlabhq/gitlabhq
> >>>>> But i have not heard if this is going to live at ASF infra
> >>>>>
> >>>>>
> >>>>>> Regards
> >>>>>> --
> >>>>>> Łukasz
> >>>>>> + 48 606 323 122 http://www.lenart.org.pl/
> >>>>>>
> >>>>>>
> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >>>>>> For additional commands, e-mail: dev-help@struts.apache.org
> >>>>>>
> >>>>>
> >>>>>
> >>>>> ---
> >>>>> http://www.grobmeier.de
> >>>>> @grobmeier
> >>>>> GPG: 0xA5CC90DB
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >>>>> For additional commands, e-mail: dev-help@struts.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>> e: davelnewton@gmail.com
> >>>> m: 908-380-8699
> >>>> s: davelnewton_skype
> >>>> t: @dave_newton <https://twitter.com/dave_newton>
> >>>> b: Bucky Bits <http://buckybits.blogspot.com/>
> >>>> g: davelnewton <https://github.com/davelnewton>
> >>>> so: Dave Newton <http://stackoverflow.com/users/438992/dave-newton>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >>> For additional commands, e-mail: dev-help@struts.apache.org
> >>
> >>
> >>
> >> ---
> >> http://www.grobmeier.de
> >> @grobmeier
> >> GPG: 0xA5CC90DB
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> >> For additional commands, e-mail: dev-help@struts.apache.org
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
Re: Svn to Git migration
Posted by Lukasz Lenart <lu...@apache.org>.
Migration to Git is almost done! Please DON'T use Subversion anymore!
https://issues.apache.org/jira/browse/INFRA-7174
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2014/1/9 Lukasz Lenart <lu...@apache.org>:
> Time to move forward
>
> https://issues.apache.org/jira/browse/INFRA-7174
>
> 2013/12/10 Christian Grobmeier <gr...@gmail.com>:
>> On 10 Dec 2013, at 7:55, Lukasz Lenart wrote:
>>
>>> I'm going postpone transition to Git as we must straighten site
>>> building first! Right now it's a real pain in the a.. and it takes
>>> ages to update site after release. Not saying about other mirror
>>> problems with this whole SvnPubSub crap :\
>>
>>
>> Oh ok. :-|
>>
>> I am a bit undecided on how we approach the website (again).
>>
>>
>>
>>
>>>
>>> Regards
>>> --
>>> Łukasz
>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>
>>> 2013/12/6 Dave Newton <da...@gmail.com>:
>>>>
>>>> Correct; pull requests are a github thing.
>>>>
>>>> And they're nice (usually).
>>>>
>>>>
>>>> On Fri, Dec 6, 2013 at 12:09 PM, Christian Grobmeier
>>>> <gr...@gmail.com>wrote:
>>>>
>>>>> On 6 Dec 2013, at 15:19, Lukasz Lenart wrote:
>>>>>
>>>>> 2013/12/6 Christian Grobmeier <gr...@gmail.com>:
>>>>>>
>>>>>>
>>>>>>> On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
>>>>>>>
>>>>>>> Do you know if git at Apache supports Pull Requests between branches?
>>>>>>>>
>>>>>>>> I've started working like that some time ago and it's awesome feature
>>>>>>>> :-)
>>>>>>>>
>>>>>>>
>>>>>>> Honestly I don't know :-)
>>>>>>>
>>>>>>> I mean you can merge between branches easily. Is that what you mean?
>>>>>>>
>>>>>>
>>>>>> Not exactly, in GitHub you can prepare a Pull Request between
>>>>>> different branches in the same repo - you don't have to fork the repo
>>>>>> at all. So you'll see the PR on issues list and you can comment,
>>>>>> change the code and so on, before merging it to mater/develop.
>>>>>>
>>>>>> But I think it's pure GitHub functionality not really related to git
>>>>>> itself.
>>>>>>
>>>>>
>>>>> I don't know for sure, but I agree, its most likely a github feature.
>>>>> I think something like gitlabhq might be able to do the same:
>>>>> https://github.com/gitlabhq/gitlabhq
>>>>> But i have not heard if this is going to live at ASF infra
>>>>>
>>>>>
>>>>>> Regards
>>>>>> --
>>>>>> Łukasz
>>>>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>
>>>>>
>>>>>
>>>>> ---
>>>>> http://www.grobmeier.de
>>>>> @grobmeier
>>>>> GPG: 0xA5CC90DB
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> e: davelnewton@gmail.com
>>>> m: 908-380-8699
>>>> s: davelnewton_skype
>>>> t: @dave_newton <https://twitter.com/dave_newton>
>>>> b: Bucky Bits <http://buckybits.blogspot.com/>
>>>> g: davelnewton <https://github.com/davelnewton>
>>>> so: Dave Newton <http://stackoverflow.com/users/438992/dave-newton>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>>
>> ---
>> http://www.grobmeier.de
>> @grobmeier
>> GPG: 0xA5CC90DB
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Lukasz Lenart <lu...@apache.org>.
Time to move forward
https://issues.apache.org/jira/browse/INFRA-7174
2013/12/10 Christian Grobmeier <gr...@gmail.com>:
> On 10 Dec 2013, at 7:55, Lukasz Lenart wrote:
>
>> I'm going postpone transition to Git as we must straighten site
>> building first! Right now it's a real pain in the a.. and it takes
>> ages to update site after release. Not saying about other mirror
>> problems with this whole SvnPubSub crap :\
>
>
> Oh ok. :-|
>
> I am a bit undecided on how we approach the website (again).
>
>
>
>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>>
>> 2013/12/6 Dave Newton <da...@gmail.com>:
>>>
>>> Correct; pull requests are a github thing.
>>>
>>> And they're nice (usually).
>>>
>>>
>>> On Fri, Dec 6, 2013 at 12:09 PM, Christian Grobmeier
>>> <gr...@gmail.com>wrote:
>>>
>>>> On 6 Dec 2013, at 15:19, Lukasz Lenart wrote:
>>>>
>>>> 2013/12/6 Christian Grobmeier <gr...@gmail.com>:
>>>>>
>>>>>
>>>>>> On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
>>>>>>
>>>>>> Do you know if git at Apache supports Pull Requests between branches?
>>>>>>>
>>>>>>> I've started working like that some time ago and it's awesome feature
>>>>>>> :-)
>>>>>>>
>>>>>>
>>>>>> Honestly I don't know :-)
>>>>>>
>>>>>> I mean you can merge between branches easily. Is that what you mean?
>>>>>>
>>>>>
>>>>> Not exactly, in GitHub you can prepare a Pull Request between
>>>>> different branches in the same repo - you don't have to fork the repo
>>>>> at all. So you'll see the PR on issues list and you can comment,
>>>>> change the code and so on, before merging it to mater/develop.
>>>>>
>>>>> But I think it's pure GitHub functionality not really related to git
>>>>> itself.
>>>>>
>>>>
>>>> I don't know for sure, but I agree, its most likely a github feature.
>>>> I think something like gitlabhq might be able to do the same:
>>>> https://github.com/gitlabhq/gitlabhq
>>>> But i have not heard if this is going to live at ASF infra
>>>>
>>>>
>>>>> Regards
>>>>> --
>>>>> Łukasz
>>>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>
>>>>
>>>>
>>>> ---
>>>> http://www.grobmeier.de
>>>> @grobmeier
>>>> GPG: 0xA5CC90DB
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>
>>>>
>>>
>>>
>>> --
>>> e: davelnewton@gmail.com
>>> m: 908-380-8699
>>> s: davelnewton_skype
>>> t: @dave_newton <https://twitter.com/dave_newton>
>>> b: Bucky Bits <http://buckybits.blogspot.com/>
>>> g: davelnewton <https://github.com/davelnewton>
>>> so: Dave Newton <http://stackoverflow.com/users/438992/dave-newton>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>
>
>
> ---
> http://www.grobmeier.de
> @grobmeier
> GPG: 0xA5CC90DB
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Christian Grobmeier <gr...@gmail.com>.
On 10 Dec 2013, at 7:55, Lukasz Lenart wrote:
> I'm going postpone transition to Git as we must straighten site
> building first! Right now it's a real pain in the a.. and it takes
> ages to update site after release. Not saying about other mirror
> problems with this whole SvnPubSub crap :\
Oh ok. :-|
I am a bit undecided on how we approach the website (again).
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2013/12/6 Dave Newton <da...@gmail.com>:
>> Correct; pull requests are a github thing.
>>
>> And they're nice (usually).
>>
>>
>> On Fri, Dec 6, 2013 at 12:09 PM, Christian Grobmeier
>> <gr...@gmail.com>wrote:
>>
>>> On 6 Dec 2013, at 15:19, Lukasz Lenart wrote:
>>>
>>> 2013/12/6 Christian Grobmeier <gr...@gmail.com>:
>>>>
>>>>> On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
>>>>>
>>>>> Do you know if git at Apache supports Pull Requests between
>>>>> branches?
>>>>>> I've started working like that some time ago and it's awesome
>>>>>> feature
>>>>>> :-)
>>>>>>
>>>>>
>>>>> Honestly I don't know :-)
>>>>>
>>>>> I mean you can merge between branches easily. Is that what you
>>>>> mean?
>>>>>
>>>>
>>>> Not exactly, in GitHub you can prepare a Pull Request between
>>>> different branches in the same repo - you don't have to fork the
>>>> repo
>>>> at all. So you'll see the PR on issues list and you can comment,
>>>> change the code and so on, before merging it to mater/develop.
>>>>
>>>> But I think it's pure GitHub functionality not really related to
>>>> git
>>>> itself.
>>>>
>>>
>>> I don't know for sure, but I agree, its most likely a github
>>> feature.
>>> I think something like gitlabhq might be able to do the same:
>>> https://github.com/gitlabhq/gitlabhq
>>> But i have not heard if this is going to live at ASF infra
>>>
>>>
>>>> Regards
>>>> --
>>>> Łukasz
>>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>
>>>
>>>
>>> ---
>>> http://www.grobmeier.de
>>> @grobmeier
>>> GPG: 0xA5CC90DB
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>>
>>
>>
>> --
>> e: davelnewton@gmail.com
>> m: 908-380-8699
>> s: davelnewton_skype
>> t: @dave_newton <https://twitter.com/dave_newton>
>> b: Bucky Bits <http://buckybits.blogspot.com/>
>> g: davelnewton <https://github.com/davelnewton>
>> so: Dave Newton <http://stackoverflow.com/users/438992/dave-newton>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
---
http://www.grobmeier.de
@grobmeier
GPG: 0xA5CC90DB
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Lukasz Lenart <lu...@apache.org>.
I'm going postpone transition to Git as we must straighten site
building first! Right now it's a real pain in the a.. and it takes
ages to update site after release. Not saying about other mirror
problems with this whole SvnPubSub crap :\
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/12/6 Dave Newton <da...@gmail.com>:
> Correct; pull requests are a github thing.
>
> And they're nice (usually).
>
>
> On Fri, Dec 6, 2013 at 12:09 PM, Christian Grobmeier <gr...@gmail.com>wrote:
>
>> On 6 Dec 2013, at 15:19, Lukasz Lenart wrote:
>>
>> 2013/12/6 Christian Grobmeier <gr...@gmail.com>:
>>>
>>>> On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
>>>>
>>>> Do you know if git at Apache supports Pull Requests between branches?
>>>>> I've started working like that some time ago and it's awesome feature
>>>>> :-)
>>>>>
>>>>
>>>> Honestly I don't know :-)
>>>>
>>>> I mean you can merge between branches easily. Is that what you mean?
>>>>
>>>
>>> Not exactly, in GitHub you can prepare a Pull Request between
>>> different branches in the same repo - you don't have to fork the repo
>>> at all. So you'll see the PR on issues list and you can comment,
>>> change the code and so on, before merging it to mater/develop.
>>>
>>> But I think it's pure GitHub functionality not really related to git
>>> itself.
>>>
>>
>> I don't know for sure, but I agree, its most likely a github feature.
>> I think something like gitlabhq might be able to do the same:
>> https://github.com/gitlabhq/gitlabhq
>> But i have not heard if this is going to live at ASF infra
>>
>>
>>> Regards
>>> --
>>> Łukasz
>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>
>>
>>
>> ---
>> http://www.grobmeier.de
>> @grobmeier
>> GPG: 0xA5CC90DB
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
>
> --
> e: davelnewton@gmail.com
> m: 908-380-8699
> s: davelnewton_skype
> t: @dave_newton <https://twitter.com/dave_newton>
> b: Bucky Bits <http://buckybits.blogspot.com/>
> g: davelnewton <https://github.com/davelnewton>
> so: Dave Newton <http://stackoverflow.com/users/438992/dave-newton>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Dave Newton <da...@gmail.com>.
Correct; pull requests are a github thing.
And they're nice (usually).
On Fri, Dec 6, 2013 at 12:09 PM, Christian Grobmeier <gr...@gmail.com>wrote:
> On 6 Dec 2013, at 15:19, Lukasz Lenart wrote:
>
> 2013/12/6 Christian Grobmeier <gr...@gmail.com>:
>>
>>> On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
>>>
>>> Do you know if git at Apache supports Pull Requests between branches?
>>>> I've started working like that some time ago and it's awesome feature
>>>> :-)
>>>>
>>>
>>> Honestly I don't know :-)
>>>
>>> I mean you can merge between branches easily. Is that what you mean?
>>>
>>
>> Not exactly, in GitHub you can prepare a Pull Request between
>> different branches in the same repo - you don't have to fork the repo
>> at all. So you'll see the PR on issues list and you can comment,
>> change the code and so on, before merging it to mater/develop.
>>
>> But I think it's pure GitHub functionality not really related to git
>> itself.
>>
>
> I don't know for sure, but I agree, its most likely a github feature.
> I think something like gitlabhq might be able to do the same:
> https://github.com/gitlabhq/gitlabhq
> But i have not heard if this is going to live at ASF infra
>
>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>
>
> ---
> http://www.grobmeier.de
> @grobmeier
> GPG: 0xA5CC90DB
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
--
e: davelnewton@gmail.com
m: 908-380-8699
s: davelnewton_skype
t: @dave_newton <https://twitter.com/dave_newton>
b: Bucky Bits <http://buckybits.blogspot.com/>
g: davelnewton <https://github.com/davelnewton>
so: Dave Newton <http://stackoverflow.com/users/438992/dave-newton>
Re: Svn to Git migration
Posted by Christian Grobmeier <gr...@gmail.com>.
On 6 Dec 2013, at 15:19, Lukasz Lenart wrote:
> 2013/12/6 Christian Grobmeier <gr...@gmail.com>:
>> On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
>>
>>> Do you know if git at Apache supports Pull Requests between
>>> branches?
>>> I've started working like that some time ago and it's awesome
>>> feature :-)
>>
>> Honestly I don't know :-)
>>
>> I mean you can merge between branches easily. Is that what you mean?
>
> Not exactly, in GitHub you can prepare a Pull Request between
> different branches in the same repo - you don't have to fork the repo
> at all. So you'll see the PR on issues list and you can comment,
> change the code and so on, before merging it to mater/develop.
>
> But I think it's pure GitHub functionality not really related to git
> itself.
I don't know for sure, but I agree, its most likely a github feature.
I think something like gitlabhq might be able to do the same:
https://github.com/gitlabhq/gitlabhq
But i have not heard if this is going to live at ASF infra
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
---
http://www.grobmeier.de
@grobmeier
GPG: 0xA5CC90DB
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Lukasz Lenart <lu...@apache.org>.
2013/12/6 Christian Grobmeier <gr...@gmail.com>:
> On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
>
>> Do you know if git at Apache supports Pull Requests between branches?
>> I've started working like that some time ago and it's awesome feature :-)
>
> Honestly I don't know :-)
>
> I mean you can merge between branches easily. Is that what you mean?
Not exactly, in GitHub you can prepare a Pull Request between
different branches in the same repo - you don't have to fork the repo
at all. So you'll see the PR on issues list and you can comment,
change the code and so on, before merging it to mater/develop.
But I think it's pure GitHub functionality not really related to git itself.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Svn to Git migration
Posted by Christian Grobmeier <gr...@gmail.com>.
On 6 Dec 2013, at 8:11, Lukasz Lenart wrote:
> Do you know if git at Apache supports Pull Requests between branches?
> I've started working like that some time ago and it's awesome feature
> :-)
Honestly I don't know :-)
I mean you can merge between branches easily. Is that what you mean?
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2013/10/16 Christian Grobmeier <gr...@gmail.com>:
>> On 16 Oct 2013, at 10:50, Lukasz Lenart wrote:
>>
>>> As far as I know, SvnPubSub doesn't support Git right now. So we can
>>> migrate struts2/trunk to Git but the rest must stay as is. And if we
>>> plan to migrate/create new user guide, it will be hosted via
>>> Subversion. Any doubts?
>>
>>
>> +1
>>
>>
>>
>>
>>
>>
>>
>>
>>>
>>> Regards
>>> --
>>> Łukasz
>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>
>>> 2013/9/18 Rene Gielen <re...@gmail.com>:
>>>>
>>>> +1
>>>>
>>>> Am 18.09.13 11:38, schrieb Lukasz Lenart:
>>>>>
>>>>> When 2.3.15.2 will be officially out, I want to send request to
>>>>> Infra
>>>>> for Svn to Git migration
>>>>>
>>>>> 2013/9/17 Christian Grobmeier <gr...@gmail.com>:
>>>>>>
>>>>>> thats fine :-) Now as we have that agreement, let's keep us
>>>>>> moving :)
>>>>>>
>>>>>> Am 17.09.13 22:48, schrieb Rene Gielen:
>>>>>>>
>>>>>>> I just wanted to get this clarified. Seems like we have an
>>>>>>> agreement
>>>>>>> :-)
>>>>>>> Am 17.09.2013 21:14 schrieb "Christian Grobmeier"
>>>>>>> <gr...@gmail.com>:
>>>>>>>
>>>>>>>> Am 17.09.13 21:06, schrieb Johannes Geppert:
>>>>>>>>>>
>>>>>>>>>> -1 for moving trunk only. We don't want to lose history, and
>>>>>>>>>> we
>>>>>>>>>> would
>>>>>>>>>> not want two repositories for one project (Struts 2). Once we
>>>>>>>>>> moved
>>>>>>>>>> to
>>>>>>>>>> git, the full struts2 svn tree should either be switched to
>>>>>>>>>> read-only
>>>>>>>>>> or/and later be removed.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Sure you are right the history should not be lost.
>>>>>>>>> What I mean is not to migrate the struts1, archive, sandbox
>>>>>>>>> and site into the new struts.git repository.
>>>>>>>>
>>>>>>>>
>>>>>>>> You speak of different things.
>>>>>>>>
>>>>>>>> This is not to migrate:
>>>>>>>> http://svn.apache.org/repos/asf/struts/
>>>>>>>> and I believe Jo is against migrating the content of all of
>>>>>>>> that. I
>>>>>>>> agree with him.
>>>>>>>>
>>>>>>>> We need to migrate this:
>>>>>>>>
>>>>>>>> http://svn.apache.org/repos/asf/struts/struts2/
>>>>>>>> including branches (there are non in short time), tags and
>>>>>>>> trunk.
>>>>>>>>
>>>>>>>> I bet you are on the same page here.
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Johannes
>>>>>>>>>
>>>>>>>>> #################################################
>>>>>>>>> web: http://www.jgeppert.com
>>>>>>>>> twitter: http://twitter.com/jogep
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2013/9/13 Rene Gielen <re...@gmail.com>
>>>>>>>>>
>>>>>>>>>> +1 for git flow as the way to go, including excellent tooling
>>>>>>>>>> -
>>>>>>>>>> command
>>>>>>>>>> line extensions, Atlassian Sourcetree support and even a IDEA
>>>>>>>>>> plugin
>>>>>>>>>> (https://github.com/OpherV/gitflow4idea) help to make this an
>>>>>>>>>> elegant
>>>>>>>>>> abstract and reliable workflow.
>>>>>>>>>>
>>>>>>>>>> -1 for moving trunk only. We don't want to lose history, and
>>>>>>>>>> we
>>>>>>>>>> would
>>>>>>>>>> not want two repositories for one project (Struts 2). Once we
>>>>>>>>>> moved
>>>>>>>>>> to
>>>>>>>>>> git, the full struts2 svn tree should either be switched to
>>>>>>>>>> read-only
>>>>>>>>>> or/and later be removed.
>>>>>>>>>>
>>>>>>>>>> +1 for dealing with ../branches/STRUTS_3_X etc as
>>>>>>>>>> hierarchical
>>>>>>>>>> feature
>>>>>>>>>> branches from which single feature branches will be forked
>>>>>>>>>> for
>>>>>>>>>> actual
>>>>>>>>>> development - at least for now. I want to investigate further
>>>>>>>>>> on
>>>>>>>>>> this
>>>>>>>>>> one, but basically there should not be a problem if we start
>>>>>>>>>> like
>>>>>>>>>> this.
>>>>>>>>>>
>>>>>>>>>> - René
>>>>>>>>>>
>>>>>>>>>> Am 12.09.13 21:48, schrieb Johannes Geppert:
>>>>>>>>>>>
>>>>>>>>>>> +1 for starting with the Git migration process.
>>>>>>>>>>>
>>>>>>>>>>> What about only migrating the current svn struts2/trunk to
>>>>>>>>>>> git and
>>>>>>>>
>>>>>>>> leave
>>>>>>>>>>>
>>>>>>>>>>> the rest in the svn repository?
>>>>>>>>>>>
>>>>>>>>>>> If we need sometime also the site in git we can request a
>>>>>>>>>>> separate
>>>>>>>>>>> git
>>>>>>>>>>> repository like struts-site.git.
>>>>>>>>>>>
>>>>>>>>>>> Johannes
>>>>>>>>>>>
>>>>>>>>>>> #################################################
>>>>>>>>>>> web: http://www.jgeppert.com
>>>>>>>>>>> twitter: http://twitter.com/jogep
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> 2013/9/11 Lukasz Lenart <lu...@apache.org>
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> I'd like to start discussion about the migration process -
>>>>>>>>>>>> there
>>>>>>>>>>>> are
>>>>>>>>>>>> few things we must clarify, at least:
>>>>>>>>>>>> - Git structure
>>>>>>>>>>>> - development flow
>>>>>>>>>>>>
>>>>>>>>>>>> I think we should have just one repo:
>>>>>>>>>>>> git.apache.org/struts.git
>>>>>>>>>>>> and
>>>>>>>>>>>> diverse versions internally via branches - so the current
>>>>>>>>>>>> S2
>>>>>>>>>>>> source
>>>>>>>>>>>> become the base and then we will transfer it to 2.5 and 3
>>>>>>>>>>>> in the
>>>>>>>>>>>> future.
>>>>>>>>>>>>
>>>>>>>>>>>> As a flow I like git-flow [1] - well known and used
>>>>>>>>>>>>
>>>>>>>>>>>> [1] https://github.com/nvie/gitflow
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Regards
>>>>>>>>>>>> --
>>>>>>>>>>>> Łukasz
>>>>>>>>>>>> + 48 606 323 122 http://www.lenart.org.pl/
>>>>>>>>>>>>
>>>>>>>>>>>> PS. It'll be implemented after cleaning up current pipeline
>>>>>>>>>>>> :-)
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> René Gielen
>>>>>>>>>> http://twitter.com/rgielen
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>>
>>>>
>>>>
>>>> --
>>>> René Gielen
>>>> http://twitter.com/rgielen
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>>> For additional commands, e-mail: dev-help@struts.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>>
>> ---
>> http://www.grobmeier.de
>> @grobmeier
>> GPG: 0xA5CC90DB
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
---
http://www.grobmeier.de
@grobmeier
GPG: 0xA5CC90DB
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org