Re: Struts 2.3.x - a new release

[Christoph Nenning]

> From: Lukasz Lenart <lukaszlen...@apache.org>
> To: Struts Developers List <dev@struts.apache.org>, 
> 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 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/jira/issues/?jql=project%20%3D%20WW%20AND%
> 20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%202.3.x%
> 20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> 
> 

Can I still cherrypick changes from PRs 54 and 55 to support-2-3 ?

Or is it too late for that?


Regards,
Christoph

This Email was scanned by Sophos Anti Virus

Re: Struts 2.3.x - a new release

[Lukasz Lenart]

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?

Not sure if it was intended, author opened the PR against "master"
branch and didn't mention "Fix Version" in the issue.


Regards
-- 
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: Struts 2.3.x - a new release

[Lukasz Lenart]

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. Nasty details.
>
>
>> > Or is it too late for that?
>>
>> Not sure if it was intended, author opened the PR against "master"
>> branch and didn't mention "Fix Version" in the issue.
>>
>
> I guess he wants it in the 2.3 series. I'll set JIRA accordingly.

Nicely handled, thanks a lot!


Regards
-- 
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: Struts 2.3.x - a new release

[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. Nasty details.


> > Or is it too late for that?
> 
> Not sure if it was intended, author opened the PR against "master"
> branch and didn't mention "Fix Version" in the issue.
> 

I guess he wants it in the 2.3 series. I'll set JIRA accordingly.



Regards,
Christoph

This Email was scanned by Sophos Anti Virus

Re: Struts 2.3.x - a new release

[Lukasz Lenart]

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/

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: Struts 2.3.x - a new release

[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.

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, 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/jira/issues/?jql=project%20%3D%20WW%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%202.3.x%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
>
>

Struts 2.3.x - a new release

[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
changes with Strict Method Invocation into to that branch?

https://issues.apache.org/jira/issues/?jql=project%20%3D%20WW%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%202.3.x%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC


Regards
-- 
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: Struts 2.3.x - a new release

[Lukasz Lenart]

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
> changes with Strict Method Invocation into to that branch?
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20WW%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%202.3.x%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: Struts 2.3.x - a new release

[Lukasz Lenart]

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 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/jira/issues/?jql=project%20%3D%20WW%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%202.3.x%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 122 http://www.lenart.org.pl/

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: Time to start new release

[Lukasz Lenart]

2014-03-31 9:35 GMT+02:00 Greg Huber gregh3...@gmail.com:
 when will it be available at

 repositories
   repository
 idapache.nexus/id
 nameASF Nexus Staging/name
 urlhttps://repository.apache.org/content/groups/staging//url
   /repository
 /repositories

It's already there


Regards
-- 
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: Time to start new release

[Greg Huber]

when will it be available at

repositories
  repository
idapache.nexus/id
nameASF Nexus Staging/name
urlhttps://repository.apache.org/content/groups/staging//url
  /repository
/repositories


On 30 March 2014 19:52, Lukasz Lenart lukaszlen...@apache.org wrote:

 Version Notes
 https://cwiki.apache.org/confluence/display/WW/Version+Notes+2.3.17

 Please take a look if everything is ok. Thanks!

 2014-03-28 21:56 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
  56 issues solved, time to start a new release :-)
 
  https://issues.apache.org/jira/browse/WW/fixforversion/12324780/
 
  2014-03-27 12:17 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
  Ok, 12 issues left
 
 
 https://issues.apache.org/jira/issues/?jql=project%20%3D%20WW%20AND%20fixVersion%20%3D%202.3.17%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
 
  2014-03-08 18:19 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
  Those issues (in most cases) will be solves with 2.3.17
 
 
 https://issues.apache.org/jira/issues/?jql=project+%3D+WW+AND+fixVersion+%3D+2.3.17+AND+status+%3D+Open+ORDER+BY+priority+DESC
 
  2014-03-06 22:30 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
  Hi,
 
  Time to start work on new release, any important issues to solve and
  include in the release?
  Thus probably will be the last 2.3.x - next will be 2.5.x (minor code
  cleanup) or 3.0 (large refactorings)
 
 
  Regards
  --
  Łukasz
  + 48 606 323 122 http://www.lenart.org.pl/

 -
 To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
 For additional commands, e-mail: dev-h...@struts.apache.org

Re: Time to start new release

[Lukasz Lenart]

Version Notes
https://cwiki.apache.org/confluence/display/WW/Version+Notes+2.3.17

Please take a look if everything is ok. Thanks!

2014-03-28 21:56 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
 56 issues solved, time to start a new release :-)

 https://issues.apache.org/jira/browse/WW/fixforversion/12324780/

 2014-03-27 12:17 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
 Ok, 12 issues left

 https://issues.apache.org/jira/issues/?jql=project%20%3D%20WW%20AND%20fixVersion%20%3D%202.3.17%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC

 2014-03-08 18:19 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
 Those issues (in most cases) will be solves with 2.3.17

 https://issues.apache.org/jira/issues/?jql=project+%3D+WW+AND+fixVersion+%3D+2.3.17+AND+status+%3D+Open+ORDER+BY+priority+DESC

 2014-03-06 22:30 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
 Hi,

 Time to start work on new release, any important issues to solve and
 include in the release?
 Thus probably will be the last 2.3.x - next will be 2.5.x (minor code
 cleanup) or 3.0 (large refactorings)


 Regards
 --
 Łukasz
 + 48 606 323 122 http://www.lenart.org.pl/

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: Time to start new release

[Johannes Geppert]

Hi Lukasz,

Looks good to me.

Great work and Thank you

Johannes

#
web: http://www.jgeppert.com
twitter: http://twitter.com/jogep


2014-03-30 20:52 GMT+02:00 Lukasz Lenart lukaszlen...@apache.org:

 Version Notes
 https://cwiki.apache.org/confluence/display/WW/Version+Notes+2.3.17

 Please take a look if everything is ok. Thanks!

 2014-03-28 21:56 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
  56 issues solved, time to start a new release :-)
 
  https://issues.apache.org/jira/browse/WW/fixforversion/12324780/
 
  2014-03-27 12:17 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
  Ok, 12 issues left
 
 
 https://issues.apache.org/jira/issues/?jql=project%20%3D%20WW%20AND%20fixVersion%20%3D%202.3.17%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC
 
  2014-03-08 18:19 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
  Those issues (in most cases) will be solves with 2.3.17
 
 
 https://issues.apache.org/jira/issues/?jql=project+%3D+WW+AND+fixVersion+%3D+2.3.17+AND+status+%3D+Open+ORDER+BY+priority+DESC
 
  2014-03-06 22:30 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
  Hi,
 
  Time to start work on new release, any important issues to solve and
  include in the release?
  Thus probably will be the last 2.3.x - next will be 2.5.x (minor code
  cleanup) or 3.0 (large refactorings)
 
 
  Regards
  --
  Łukasz
  + 48 606 323 122 http://www.lenart.org.pl/

 -
 To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
 For additional commands, e-mail: dev-h...@struts.apache.org

Re: Time to start new release

[Rene Gielen]

Looks good.

Great job, you are a machine ;)

- René

Am 30.03.14 20:52, schrieb Lukasz Lenart:
 Version Notes
 https://cwiki.apache.org/confluence/display/WW/Version+Notes+2.3.17
 
 Please take a look if everything is ok. Thanks!
 
 2014-03-28 21:56 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
 56 issues solved, time to start a new release :-)

 https://issues.apache.org/jira/browse/WW/fixforversion/12324780/

 2014-03-27 12:17 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
 Ok, 12 issues left

 https://issues.apache.org/jira/issues/?jql=project%20%3D%20WW%20AND%20fixVersion%20%3D%202.3.17%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC

 2014-03-08 18:19 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
 Those issues (in most cases) will be solves with 2.3.17

 https://issues.apache.org/jira/issues/?jql=project+%3D+WW+AND+fixVersion+%3D+2.3.17+AND+status+%3D+Open+ORDER+BY+priority+DESC

 2014-03-06 22:30 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
 Hi,

 Time to start work on new release, any important issues to solve and
 include in the release?
 Thus probably will be the last 2.3.x - next will be 2.5.x (minor code
 cleanup) or 3.0 (large refactorings)


 Regards
 --
 Łukasz
 + 48 606 323 122 http://www.lenart.org.pl/
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
 For additional commands, e-mail: dev-h...@struts.apache.org
 


-- 
René Gielen
http://twitter.com/rgielen

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: Time to start new release

[Lukasz Lenart]

56 issues solved, time to start a new release :-)

https://issues.apache.org/jira/browse/WW/fixforversion/12324780/

2014-03-27 12:17 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
 Ok, 12 issues left

 https://issues.apache.org/jira/issues/?jql=project%20%3D%20WW%20AND%20fixVersion%20%3D%202.3.17%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC

 2014-03-08 18:19 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
 Those issues (in most cases) will be solves with 2.3.17

 https://issues.apache.org/jira/issues/?jql=project+%3D+WW+AND+fixVersion+%3D+2.3.17+AND+status+%3D+Open+ORDER+BY+priority+DESC

 2014-03-06 22:30 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
 Hi,

 Time to start work on new release, any important issues to solve and
 include in the release?
 Thus probably will be the last 2.3.x - next will be 2.5.x (minor code
 cleanup) or 3.0 (large refactorings)


 Regards
 --
 Łukasz
 + 48 606 323 122 http://www.lenart.org.pl/

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: Time to start new release

[Lukasz Lenart]

Ok, 12 issues left

https://issues.apache.org/jira/issues/?jql=project%20%3D%20WW%20AND%20fixVersion%20%3D%202.3.17%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC

2014-03-08 18:19 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
 Those issues (in most cases) will be solves with 2.3.17

 https://issues.apache.org/jira/issues/?jql=project+%3D+WW+AND+fixVersion+%3D+2.3.17+AND+status+%3D+Open+ORDER+BY+priority+DESC

 2014-03-06 22:30 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
 Hi,

 Time to start work on new release, any important issues to solve and
 include in the release?
 Thus probably will be the last 2.3.x - next will be 2.5.x (minor code
 cleanup) or 3.0 (large refactorings)


 Regards
 --
 Łukasz
 + 48 606 323 122 http://www.lenart.org.pl/

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: Time to start new release

[Lukasz Lenart]

Those issues (in most cases) will be solves with 2.3.17

https://issues.apache.org/jira/issues/?jql=project+%3D+WW+AND+fixVersion+%3D+2.3.17+AND+status+%3D+Open+ORDER+BY+priority+DESC

2014-03-06 22:30 GMT+01:00 Lukasz Lenart lukaszlen...@apache.org:
 Hi,

 Time to start work on new release, any important issues to solve and
 include in the release?
 Thus probably will be the last 2.3.x - next will be 2.5.x (minor code
 cleanup) or 3.0 (large refactorings)


 Regards
 --
 Łukasz
 + 48 606 323 122 http://www.lenart.org.pl/

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Time to start new release

[Lukasz Lenart]

Hi,

Time to start work on new release, any important issues to solve and
include in the release?
Thus probably will be the last 2.3.x - next will be 2.5.x (minor code
cleanup) or 3.0 (large refactorings)


Regards
-- 
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: A new release

[Lukasz Lenart]

2011/2/18 Martin Cooper mart...@apache.org:
 Besides it's more about promoting a release. I was asking about that
 sometime ago. It would be great to promote Betas or RCs without
 calling for a Vote.

 There is no such thing as a release without a vote. Every release must
 be voted on by the PMC, no exceptions. It doesn't matter how it's
 labeled.

I've read throughout all the docs I found out and now it's a bit clear
for me - release and build - I was mixing these terms ;-)
Anyway, as you said, there is no release without a vote. I was
thinking about a test build, but right now we have snapshots, so it
should be sufficient.

I'm still missing something, but it's just matter of time to figure
out how it should be / how it works ;-)
The second thing, the whole talk about preparing the release plan
should be included into the release 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, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: A new release

[Lukasz Lenart]

2011/2/17 Wendy Smoak wsm...@gmail.com:
 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 labeling
 it GA. ;)

OK, thanks :-)

 The convention here (decided long ago) is to use plain numbered
 versions like 2.3.4 and apply a quality label to them later.  It's not
 clear whether you want to change that, but if so I'd suggest digging
 back through the archives to understand why it was done and then
 starting a separate thread to discuss.

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.


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.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: A new release

[Lukasz Lenart]

W dniu 17 lutego 2011 16:07 użytkownik Dave Newton
davelnew...@gmail.com 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

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: A new release

[Wendy Smoak]

On Thu, Feb 17, 2011 at 10:01 AM, Lukasz Lenart
lukasz.len...@googlemail.com 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 tested it and it works for your
project, who cares what the Struts developers think. ;)

One of the reasons it was done is to eliminate double work.  If you
use version 5.4.3-Beta for a while and decide that it's GA, then you
have to re-do the release process to re-label the artifacts, and do
another round of testing.  Ditto with RC1, RC2, once you decide this
is the one then you have to re-do the process one last time.

Once upon a time, this method of versioning had the happy side effect
of letting some of use more bleeding edge versions in production,
since we could say to the powers that be with a straight face, I'm
using version 3.8.2 and just... not mention... that it's only a
beta version. ;)

Another is that it's hard to know whether something is *really* GA
until it gets beat on for a while.  Sure we tested as much as we
could, but it's much easier to promote something after a couple of
weeks than is to have to retract a GA release that turned out to have
a fatal flaw.

Anyway... I don't have a dog in this fight anymore, but if you want to
change the versioning scheme then start a new thread with a
[PROPOSAL].

-- 
Wendy

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: A new release

[Lukasz Lenart]

2011/2/17 Wendy Smoak wsm...@gmail.com:
 But does it matter?  If you've tested it and it works for your
 project, who cares what the Struts developers think. ;)

No, but it gives me a clear signal what can be the origin of my problem.

 One of the reasons it was done is to eliminate double work.  If you
 use version 5.4.3-Beta for a while and decide that it's GA, then you
 have to re-do the release process to re-label the artifacts, and do
 another round of testing.  Ditto with RC1, RC2, once you decide this
 is the one then you have to re-do the process one last time.

It isn't a problem anymore, with Nexus on our side is just few steps
to prepare a release ;-)

 Another is that it's hard to know whether something is *really* GA
 until it gets beat on for a while.  Sure we tested as much as we
 could, but it's much easier to promote something after a couple of
 weeks than is to have to retract a GA release that turned out to have
 a fatal flaw.

Yep, that's the one of the reasons I have, another is that we fixed 41
bugs of total 50 assigned to 2.2.2 version. The most important are
done, the rest is related 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 faster ;-)

Besides it's more about promoting a release. I was asking about that
sometime ago. It would be great to promote Betas or RCs without
calling for a Vote.

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 ?


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.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: A new release

[Wendy Smoak]

On Thu, Feb 17, 2011 at 10:35 AM, Lukasz Lenart
lukasz.len...@googlemail.com 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.markmail.org/search/?q=release%20version#query:release%20version%20list%3Aorg.apache.struts.dev%20date%3A200308-200504%20+page:1+mid:byisn6isnyq25lsr+state:results

 Besides it's more about promoting a release. I was asking about that
 sometime ago. It would be great to promote Betas or RCs without
 calling for a Vote.

What do you mean?

-- 
Wendy

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: A new release

[Martin Cooper]

On Thu, Feb 17, 2011 at 7:35 AM, Lukasz Lenart
lukasz.len...@googlemail.com wrote:
 2011/2/17 Wendy Smoak wsm...@gmail.com:

snip/

 Yep, that's the one of the reasons I have, another is that we fixed 41
 bugs of total 50 assigned to 2.2.2 version. The most important are
 done, the rest is related 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 faster ;-)

Yup, especially since you will find me *extremely* hard to convince. :-)

 Besides it's more about promoting a release. I was asking about that
 sometime ago. It would be great to promote Betas or RCs without
 calling for a Vote.

There is no such thing as a release without a vote. Every release must
be voted on by the PMC, no exceptions. It doesn't matter how it's
labeled.

Just to be clear, we start by building what we call a Test Build, with
the latest 3-part number. That Test Build is made available to
developers (i.e. dev@ only). After it's been available for long enough
that people have had a chance to determine how stable it is, we vote
on whether it should become a Beta release, a GA release, or not a
release at all.

As Wendy has implied, we vote on actual bits. That means that if we
had created a build as an RC, we would need to vote on it to release
the RC, and if everyone thought it was good enough to be GA, we would
need to re-roll the release with the new name (i.e. not RC now), and
vote on it *again*, because the bits are different. I don't think
that's what you want.

Having been Release Manager for about a dozen releases of Struts over
the years (not counting test builds that didn't make releases),
including through the transition from the old scheme to the new one, I
can tell you, you don't want to go back.

--
Martin Cooper


 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 ?


 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.org
 For additional commands, e-mail: dev-h...@struts.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: A new release

[Martin Cooper]

On Mon, Jan 31, 2011 at 10:52 PM, Lukasz Lenart
lukasz.len...@googlemail.com wrote:
 2011/1/31 Paul Benedict pbened...@apache.org:
 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. Otherwise, beta can be published too. Alpha
 will just stay a developer build.

 It's quite uncommon, thanks Paul :-)

Actually, it's not. If you look around even just the ASF, you'll find
that a number of the best-known ASF projects use this same scheme. In
fact, we didn't invent it, we adopted it from those projects.

--
Martin Cooper



 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.org
 For additional commands, e-mail: dev-h...@struts.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: A new release

[Lukasz Lenart]

2011/1/31 Paul Benedict pbened...@apache.org:
 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. Otherwise, beta can be published too. Alpha
 will just stay a developer build.

It's quite uncommon, thanks Paul :-)


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.org
For additional commands, e-mail: dev-h...@struts.apache.org

A new release

[Lukasz Lenart]

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.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: A new release

[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
[ ] Alpha

If it's GA, it's production. Otherwise, beta can be published too. Alpha
will just stay a developer build.

Paul

On Mon, Jan 31, 2011 at 1:31 AM, Lukasz Lenart lukasz.len...@googlemail.com
 wrote:

 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.org
 For additional commands, e-mail: dev-h...@struts.apache.org

OGNL 3.0 and new release

[Lukasz Lenart]

Hi,

The new release is blocked by OGNL 3.0 right now - it's still not in
central repo. The rest of issues are quite simple to solve and I would
be ready to make the release very soon. There were two or three major
issues solved with OGNL release and I think they are imported to
improve Struts 2 as well.

Can someone help to push it to central repo?


Regards
-- 
Łukasz
http://www.lenart.org.pl/
Kapituła Javarsovia 2010
http://javarsovia.pl

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: New release

[Lukasz Lenart]

I registered a Wish to upload OGNL 3.0 to Maven Central repo, after
that I will be able to make a release.


Regards
-- 
Łukasz
http://www.lenart.org.pl/
Kapituła Javarsovia 2010
http://javarsovia.pl

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: New release

[Lukasz Lenart]

2010/3/16 Dale Newfield d...@newfield.org:
 151 and 157 appear to have fixes in the issues...any chance we can
 incorporate them, too?

I don't know how to test them, without real test cases I will not
implement those changes!

I made used below test case for 151 and it went smoothly with and
without changes:

public void testNestedASTOrExpressions() throws Exception {
// given
String expression = 't1' + ('t2' || 't3');
OgnlContext context = new OgnlContext();

// when
Node value = Ognl.compileExpression(context, null, expression);

// then
assertEquals(t1t2, value.getValue(context, null));
}

For 157 I tried below test case after implementing the change but it
throws java.lang.IllegalArgumentException: argument type mismatch

public void testMethodWithoutVarargsParameters() throws Exception {
// given
String expression = clear();
OgnlContext context = new OgnlContext();
StringChild root = new StringChild();

// when
Node value = Ognl.compileExpression(context, root, expression);

// then
assertEquals(t1t2, value.getValue(context, root));
}


Regards
-- 
Łukasz
http://www.lenart.org.pl/
Kapituła Javarsovia 2010
http://javarsovia.pl

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: New release

[Dale Newfield]

Thanks for working on this, Łukasz!

-Dale


-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: New release

[Lukasz Lenart]

I noticed that we have branches for 2.x and 2.1.x. Should I make a
branch for 2.2.x as well after releasing it or before?


Regards
-- 
Łukasz
http://www.lenart.org.pl/
Kapituła Javarsovia 2010
http://javarsovia.pl

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: New release

[Lukasz Lenart]

I made a new release of OGNL 3.0, right now I'm trying to push it into
central repo?


Regards
-- 
Łukasz
http://www.lenart.org.pl/
Kapituła Javarsovia 2010
http://javarsovia.pl

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: New release

[Andreas Joseph Krogh]

On Tuesday 16. March 2010 11.04.29 Lukasz Lenart wrote:
 I made a new release of OGNL 3.0, right now I'm trying to push it into
 central repo?

Can you post a link to changes in 3.0?

-- 
Andreas Joseph Krogh andr...@officenet.no
Senior Software Developer / CTO
+-+
OfficeNet AS| The most difficult thing in the world is to |
Rosenholmveien 25   | know how to do a thing and to watch |
1414 Trollåsen  | somebody else doing it wrong, without   |
NORWAY  | comment.|
| |
Tlf:+47 24 15 38 90 | |
Fax:+47 24 15 38 91 | |
Mobile: +47 909  56 963 | |
+-+

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: New release

[Lukasz Lenart]

2010/3/16 Andreas Joseph Krogh andr...@officenet.no:
 On Tuesday 16. March 2010 11.04.29 Lukasz Lenart wrote:
 I made a new release of OGNL 3.0, right now I'm trying to push it into
 central repo?

 Can you post a link to changes in 3.0?

http://jira.opensymphony.com/secure/IssueNavigator.jspa?reset=truepid=10090fixfor=21770

except 145 - I thing it's a work for future


Regards
-- 
Łukasz
http://www.lenart.org.pl/
Kapituła Javarsovia 2010
http://javarsovia.pl

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: New release

[Lukasz Lenart]

I'm planning to merge 2.1.9 to 2.2.0 in JIRA to make a clean up and
drop 2.1.9 from RoadMap, any doubts?


Regards
-- 
Łukasz
http://www.lenart.org.pl/
Kapituła Javarsovia 2010
http://javarsovia.pl

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: New release

[Dale Newfield]

Lukasz Lenart wrote:

Andreas Joseph Krogh asked:

Can you post a link to changes in 3.0?


http://jira.opensymphony.com/secure/IssueNavigator.jspa?reset=truepid=10090fixfor=21770
except 145 - I thing it's a work for future


151 and 157 appear to have fixes in the issues...any chance we can 
incorporate them, too?


-Dale

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: New release

[Wes Wannemacher]

will this be 2.1.9 or 2.2.0 ?

On Wed, Mar 10, 2010 at 5:12 PM, Lukasz Lenart
lukasz.len...@googlemail.com wrote:
 Hi,

 I want to make a new release of Struts 2 project. The steps are as follow:
 - release new OGNL version 3.0
 - move Struts 2 archetypes inside Struts 2 main folder (as it was with XWork)
 - make a release

 We have 2 issues solved for OGNL (I'm checking one regarding
 efficiency), 7 for XWork and 27 for Struts 2 (fixed for 2.1.9, 2.2.x,
 2.2.0). I will try to do it during next week.


 Regards
 --
 Łukasz
 http://www.lenart.org.pl/
 Kapituła Javarsovia 2010
 http://javarsovia.pl

 -
 To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
 For additional commands, e-mail: dev-h...@struts.apache.org





-- 
Wes Wannemacher

Head Engineer, WanTii, Inc.
Need Training? Struts, Spring, Maven, Tomcat...
Ask me for a quote!

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: New release

[Haroon Rafique]

On Today at 11:12pm, LL=Lukasz Lenart lukasz.len...@googlemail.com wrote:

LL Hi,
LL 
LL I want to make a new release of Struts 2 project. The steps are as follow:
LL - release new OGNL version 3.0
LL - move Struts 2 archetypes inside Struts 2 main folder (as it was with 
XWork)
LL - make a release
LL 
LL We have 2 issues solved for OGNL (I'm checking one regarding
LL efficiency), 7 for XWork and 27 for Struts 2 (fixed for 2.1.9, 2.2.x,
LL 2.2.0). I will try to do it during next week.
LL 
LL 
LL Regards
LL 

Hi Lukasz,

Any chance XW-737 can be fixed (patch available) and made part of the 
release?

Cheers,
--
Haroon Rafique
haroon.rafi...@utoronto.ca


-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Re: New release

[Lukasz Lenart]

2010/3/11 Haroon Rafique haroon.rafi...@utoronto.ca:
 Any chance XW-737 can be fixed (patch available) and made part of the
 release?

Solved, thanks!


Regards
-- 
Łukasz
http://www.lenart.org.pl/
Kapituła Javarsovia 2010
http://javarsovia.pl

-
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

DO NOT REPLY [Bug 30997] New: - Release notes reference ActionErrors as deprecated

[bugzilla]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=30997.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30997

Release notes reference ActionErrors as deprecated

   Summary: Release notes reference ActionErrors as deprecated
   Product: Struts
   Version: Nightly Build
  Platform: Other
OS/Version: Other
Status: NEW
  Severity: Normal
  Priority: Other
 Component: Documentation
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The release notes (release-notes.xml?rev=1.61) for 1.2.2 contain the following
in the What's new? section:

Although not removed, in many cases you should replace the deprecated
ActionErrors with the preferred ActionMessages to ensure correct operation.

However, the ActionErrors class is not actually deprecated.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]