I have tested it the past 3 hours with my release and so far it looks
good to me.
I was specifically looking at WW-4037, which I actually use.
Looking more at it on sunday, but if you hear nothing from me, nothing
has changed on what I said.
Cheers
Christian
On Fri, Jun 14, 2013 at 1:16 PM, Luk
Hi,
Please take a time and test the bits - any help is appreciated. If
there be no problem, I'm going to start Vote next week around
Wednesday
Staging Maven repo
https://repository.apache.org/content/groups/staging/
Standalone artifacts
http://people.apache.org/builds/struts/2.3.15/
Release not
Hi all,
my team has moved from CVS to GIT few months ago
and besides the obvious benefits
there are two things that surprised us.
One is the speed of working with GIT,
we were hoping to get more speedup
and after the transition only branching is faster.
Second thing is complication of versioning
+1 all 'round; the ability to work off-line on multiple branches, the
ability to cherry-pick merges, etc. is so helpful.
I haven't done anything with versioned releases, not am I sure what the
best practice is.
I have started using gitflow too, which seems nice, and a decent way to
normalize proc
Christian
I spent the better part of yesterday pulling source project whose plugin was
abending in eclipse..
I vote for a 3 part approval
1)Functionality Reason(s)
e.g. Supports Tagging Branch-Labels..snapshots...pullling deltas instead of the
whole nine yards
2)IDE Support:
e.g. *workable* pl
2013/6/14 Christian Grobmeier :
> Hello folks,
>
> how do we deal with pull requests in general?
> This one of course is not applicable, but do we have a procedure to
> deal with them?
>
> In theory, we could include the code with something like that:
> wiki.apache.org/logging/UsingGitWithLogging
>
Hello,
I would like to collect some feelings on GIT here. We have discussed a
bit to move on to Git for S3. If we would vote on it today, what would
you vote?
Personally I would vote +1.
There is of course a risk that things become complicated first. But
there is a lot of experience with in ASF
Hello folks,
how do we deal with pull requests in general?
This one of course is not applicable, but do we have a procedure to
deal with them?
In theory, we could include the code with something like that:
wiki.apache.org/logging/UsingGitWithLogging
But we would need to make sure we got an ICLA
2013/6/14 Christian Grobmeier :
> On Fri, Jun 14, 2013 at 9:34 AM, Lukasz Lenart
> wrote:
>> 2013/6/13 Christian Grobmeier :
>>> On Thu, Jun 13, 2013 at 9:40 PM, Lukasz Lenart
>>> wrote:
2013/6/13 Christian Grobmeier :
> for future reference, what did you do?
Re-edited page o
+1
Il giorno 14/giu/2013 09:34, "Lukasz Lenart" ha
scritto:
> 2013/6/13 Christian Grobmeier :
> > On Thu, Jun 13, 2013 at 9:40 PM, Lukasz Lenart
> wrote:
> >> 2013/6/13 Christian Grobmeier :
> >>> for future reference, what did you do?
> >>
> >> Re-edited page on Confluence to trigger auto-expor
On Fri, Jun 14, 2013 at 9:34 AM, Lukasz Lenart wrote:
> 2013/6/13 Christian Grobmeier :
>> On Thu, Jun 13, 2013 at 9:40 PM, Lukasz Lenart
>> wrote:
>>> 2013/6/13 Christian Grobmeier :
for future reference, what did you do?
>>>
>>> Re-edited page on Confluence to trigger auto-export and then
2013/6/13 Christian Grobmeier :
> On Thu, Jun 13, 2013 at 9:40 PM, Lukasz Lenart
> wrote:
>> 2013/6/13 Christian Grobmeier :
>>> for future reference, what did you do?
>>
>> Re-edited page on Confluence to trigger auto-export and then I have
>> launched my fancy script to update Draft docs and af
12 matches
Mail list logo
