2015-10-12 13:31 GMT+02:00 Christoph Nenning :
>> > Can I still cherrypick changes from PRs 54 and 55 to support-2-3 ?
>>
>> It isn't possible :) I meant, XWork was moved into struts-core so
>> cherry-picking will create a file in wrong place. You can manually
>> apply the change.
>>
>
> Oh, yes. N
> > Can I still cherrypick changes from PRs 54 and 55 to support-2-3 ?
>
> It isn't possible :) I meant, XWork was moved into struts-core so
> cherry-picking will create a file in wrong place. You can manually
> apply the change.
>
Oh, yes. Nasty details.
> > Or is it too late for that?
>
> N
2015-10-12 12:57 GMT+02:00 Christoph Nenning :
> Can I still cherrypick changes from PRs 54 and 55 to support-2-3 ?
It isn't possible :) I meant, XWork was moved into struts-core so
cherry-picking will create a file in wrong place. You can manually
apply the change.
> Or is it too late for that?
> From: Lukasz Lenart
> To: Struts Developers List ,
> Date: 09.10.2015 17:55
> Subject: Struts 2.3.x - a new release
>
> Hi,
>
> I am going to spend some time on preparing a new 2.3.x release, there
> is already few issues registered. All the work will be per
2015-10-10 11:08 GMT+02:00 Johannes Geppert :
> Hi,
>
> I think SMI has a high impact and should be better a feature for 2.5 only.
> Cause this can break some existing apps and is may not a "drop in" upgrade
> only.
You are right :)
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Hi,
I think SMI has a high impact and should be better a feature for 2.5 only.
Cause this can break some existing apps and is may not a "drop in" upgrade
only.
Johannes
Am 09.10.2015 5:56 nachm. schrieb "Lukasz Lenart" :
> Hi,
>
> I am going to spend some time on preparing a new 2.3.x release, t
Woops! Just noticed that I have created the branch based on "master"
but I should use some of the STRUTS_2_3_x tags, will do it right now.
2015-10-09 17:58 GMT+02:00 Lukasz Lenart :
> I meant the "support-2-3" branch ;-)
>
> 2015-10-09 17:56 GMT+02:00 Lukasz Lenart :
>> Hi,
>>
>> I am going to spe
I meant the "support-2-3" branch ;-)
2015-10-09 17:56 GMT+02:00 Lukasz Lenart :
> Hi,
>
> I am going to spend some time on preparing a new 2.3.x release, there
> is already few issues registered. All the work will be performed in
> the "struts-2-3" branch. I am also wondering if I should merge the
Hi,
I am going to spend some time on preparing a new 2.3.x release, there
is already few issues registered. All the work will be performed in
the "struts-2-3" branch. I am also wondering if I should merge the
changes with Strict Method Invocation into to that branch?
https://issues.apache.org/jir
se page - it explains a lot - many
thanks Wendy!
Ok, let's start preparing a new release ... ;-)
Kind regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Kapituła Javarsovia http://javarsovia.pl
-
To unsubscribe
On Mon, Jan 31, 2011 at 10:52 PM, Lukasz Lenart
wrote:
> 2011/1/31 Paul Benedict :
>> He he.. I'll give you the answer that I got whenever I wanted to do "beta"
>> releases. Votes determine the quality of the release, not the version label.
>> So 2.2.2 could be production if it's voted that way. W
everyone uses) or
> development improvement. Few users requested a new release, especially
> that the most important bugs are done. So I can just postpone those
> bugs and prepare a new release or start a new thread about changing
> labeling. Hmmm preparing a new release will be faster ;
On Thu, Feb 17, 2011 at 10:35 AM, Lukasz Lenart
wrote:
> I was looking for that discussion about labeling but didn't find,
> could you help and point to the right direction ? Maybe it was on PMC
> group ?
I poked around on MarkMail and found some discussion in late 2004.
Try this:
http://struts
ated to JSONPlugin (not everyone uses) or
development improvement. Few users requested a new release, especially
that the most important bugs are done. So I can just postpone those
bugs and prepare a new release or start a new thread about changing
labeling. Hmmm preparing a new release will be fast
On Thu, Feb 17, 2011 at 10:01 AM, Lukasz Lenart
wrote:
> The answer is simple: I'm using Maven for development basis and it's
> easy for me to switch between versions. I don't need to go to a web
> page to check if 2.2.2 is a Beta or GA. I see it just in my pom.
But does it matter? If you've te
W dniu 17 lutego 2011 16:07 użytkownik Dave Newton
napisał:
> Why not RCn?
Fine for me, RC or Beta it's just a signal to community, work in
progress, stay tune
Kind regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Kapituła Javarsovia http://javarsovia.pl
--
Why not RCn?
Dave
On Feb 17, 2011 10:02 AM, "Lukasz Lenart"
wrote:
> 2011/2/17 Wendy Smoak :
>> As release manager you can frame the vote however you want. If you
>> have specific reasons for calling it a Beta release (unfinished
>> feature, API not yet locked down,) then you can mention them.
2011/2/17 Wendy Smoak :
> As release manager you can frame the vote however you want. If you
> have specific reasons for calling it a Beta release (unfinished
> feature, API not yet locked down,) then you can mention them. It's
> unlikely the rest of the dev team will revolt and insist on labelin
On Thu, Feb 17, 2011 at 9:11 AM, Lukasz Lenart
wrote:
> So, is it possible to call for a Vote just with the [] Beta option ?
> If the Votes passes, the release can be officially promoted to Maven
> Central Repo as a Beta, if not, it can be deleted.
As release manager you can frame the vote howeve
I was thinking about that and there isn't possible to release Struts
2.2.2-BETA1, I mean, the intention is to always release a GA version,
but during the Vote process it can be changed to a Beta. My point of
view is more from technical perspective. Before calling a Vote I must
walk through Maven re
2011/1/31 Paul Benedict :
> He he.. I'll give you the answer that I got whenever I wanted to do "beta"
> releases. Votes determine the quality of the release, not the version label.
> So 2.2.2 could be production if it's voted that way. When you put out your
> vote, ask:
>
> [ ] GA
> [ ] Beta
> [ ]
He he.. I'll give you the answer that I got whenever I wanted to do "beta"
releases. Votes determine the quality of the release, not the version label.
So 2.2.2 could be production if it's voted that way. When you put out your
vote, ask:
[ ] GA
[ ] Beta
[ ] Alpha
If it's GA, it's production. Othe
Hi all!
What about releasing a new version, say 2.2.2-BETA1 ?
Kind regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
Kapituła Javarsovia http://javarsovia.pl
-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.o
23 matches
Mail list logo
