Unfortunately, I dropped out of my education in the second year as a
monk in the order of the crippled mantis.
But I'll invite Tom and Musachy, and as soon as our myspace page is
set up, we'll post an announcement with a link to the video.
Thanks,
Phil
On 2/19/07, Tom Schneider <[EMAIL PROTECT
To make sure everything is reviewed, I look for the tickets without a
fix version set (which maps to "unknown"), and then set the ticket to
an upcoming milestone or a release series, or to Future. I don't
consider Future the horizon, but beyond the horizon. The horizon is
the numbered versions. If
Would a layout like Groovy make what we have more accessible?
* http://groovy.codehaus.org/
On 2/14/07, Philip Luppens <[EMAIL PROTECTED]> wrote:
Ok, sounds fine to me. Then we'll drop the User Guide, and start
writing on those missing chapters.
Btw, the crud tutorial: should we make a part II
The Struts 2.0.6 test build is now available.
Release notes:
* http://struts.apache.org/2.x/docs/release-notes-206.html
Distribution:
* http://people.apache.org/builds/struts/2.0.6/
Maven 2 staging repository:
* http://people.apache.org/builds/struts/2.0.6/m2-staging-repository/
Once yo
+1 for GA
-
Posted via Jive Forums
http://forums.opensymphony.com/thread.jspa?threadID=65672&messageID=125490#125490
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
On 2/19/07, Ted Husted <[EMAIL PROTECTED]> wrote:
To make sure everything is reviewed, I look for the tickets without a
fix version set (which maps to "unknown"), and then set the ticket to
an upcoming milestone or a release series, or to Future. I don't
consider Future the horizon, but beyond t
[ ] Leave at test build
[ ] Alpha
[ ] Beta
[X] General Availability (GA)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--- Ted Husted <[EMAIL PROTECTED]> wrote:
> [ X ] General Availability (GA)
So you get at least one user vote :)
Dave
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.y
Ted,
I was hoping that it would be obvious that version 1.x or whatever is sooner
than Future :-) So when I talk about Future being on the horizon, yes, the
issues have been reviewed and the ticket is viable, but it's not slated for
the near future.
However, what about tickets that are reviewed
Perhaps instead of using a 1.x category, it might be more useful to
tag issues 1.4.x or 1.5.x categories, and then "Future" for anything
else.. So perhaps the 1.x issues that are not on the front-burner for
1.4.x should be marked Future, and the 1.x category retired.
There may not be current inte
On 2/19/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
Ted,
I was hoping that it would be obvious that version 1.x or whatever is
sooner
than Future :-) So when I talk about Future being on the horizon, yes, the
issues have been reviewed and the ticket is viable, but it's not slated
for
the near
The purpose of the Road Map is to assign issues to a release. Since "Future"
is not a version or a release -- but just a grouping of issues for the
"future" -- it has little use, and the way we use it tells me we're using
the Road Map wrongly. Now, I believe that's the case, but I am not going to
On 2/19/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
The purpose of the Road Map is to assign issues to a release. Since "Future"
is not a version or a release -- but just a grouping of issues for the
"future" -- it has little use, and the way we use it tells me we're using
the Road Map wrongly.
On 2/19/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
The purpose of the Road Map is to assign issues to a release. Since
"Future"
is not a version or a release -- but just a grouping of issues for the
"future" -- it has little use, and the way we use it tells me we're using
the Road Map wrongly.
From that perspective, the underlying problem is that JIRA puts every
"release" on the "roadmap" whether we want it to or not. It's not
that we are using JIRA wrongly, only that JIRA, like any off-the-shelf
product, is imperfect.
We are mapping what we want to do to the JIRA system, the best wa
Thank you for everyone's input. I do see the reason behind why having a
TBD/Future is preferred by many people. I also find value in quickly
determining which issues have been reviewed vs. new issues. Thus, I shall
lay down my gauntlet!
husted wrote:
>
> [X] General Availability (GA)
>
Tested with AppFuse 2.x (JDK 6, Maven 2.0.5, Tomcat 5.5.17 on OS X) and all
tests pass.
Matt
--
View this message in context:
http://www.nabble.com/-VOTE--Struts-2.0.6-Quality-tf3253694.html#a9054691
Sent from the Struts - Dev mailing lis
17 matches
Mail list logo
