> 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
>
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.
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
>>
> > 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?
>
>
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
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
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?
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
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
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
://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
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
/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
:
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
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
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
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
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
, 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
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
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
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
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
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.
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
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
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
[
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:
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.
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
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:
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
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
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
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
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
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
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:
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
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
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
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
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.
43 matches
Mail list logo