. If someone can confirm
that's
all this is, and show me exactly what needs to change, I can get that
done this weekend.
-Original Message-
From: Joe Germuska [mailto:[EMAIL PROTECTED]
Sent: Friday, February 20, 2004 12:12 PM
To: Struts Developers List
Subject: Re: [VOTE] 1.2.0 Release
.
-Original Message-
From: Joe Germuska [mailto:[EMAIL PROTECTED]
Sent: Friday, February 20, 2004 12:12 PM
To: Struts Developers List
Subject: Re: [VOTE] 1.2.0 Release Plan
At 1:49 PM -0600 2/20/04, Joe Germuska wrote:
Just a few things:
* What about
, February 20, 2004 12:12 PM
To: Struts Developers List
Subject: Re: [VOTE] 1.2.0 Release Plan
At 1:49 PM -0600 2/20/04, Joe Germuska wrote:
Just a few things:
* What about the new Apache license? Technically, it doesn't need
-Original Message-
From: Karr, David [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 21, 2004 12:46 AM
To: 'Struts Developers List'
Subject: RE: [VOTE] 1.2.0 Release Plan
Does this involve changing the file header comment to replace the
existing license with the new license
-Original Message-
From: Paul Sundling [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 21, 2004 7:52 AM
To: Struts Developers List
Subject: Re: [VOTE] 1.2.0 Release Plan
David Karr emailed me, so I'll take care of the licenses this weekend.
I have a social engagement today
-Original Message-
From: Joe Germuska [mailto:[EMAIL PROTECTED]
Sent: Friday, February 20, 2004 11:50 AM
To: Struts Developers List
Subject: Re: [VOTE] 1.2.0 Release Plan
Just a few things:
* What about the new Apache license? Technically, it doesn't need to
change
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 21, 2004 8:10 AM
To: Struts Developers List
Subject: Re: [VOTE] 1.2.0 Release Plan
-Original Message-
From: Karr, David [mailto:[EMAIL PROTECTED]
Sent: Saturday, February
20, 2004 12:12 PM
To: Struts Developers List
Subject: Re: [VOTE] 1.2.0 Release Plan
At 1:49 PM -0600 2/20/04, Joe Germuska wrote:
Just a few things:
* What about the new Apache license? Technically, it doesn't need
to change if we release
'
Subject: Re: [VOTE] 1.2.0 Release Plan
I woke up earlier than planned (I'm on a strange sleep schedule) and
Robert Leland got me a copy of the tools, which saved me a bunch of time
since my own tool was only 40% done. I used the java one, since python
is the one LAMP language I don't know
David Graham,
I finished 3 minutes ahead of my estimated time. :) Unfortunately, it's
taking forever (30 minutes so far) to upload the patch file, which is
just shy of 2 megs. Would it speed things up any to send you a copy
directly, while it's uploading? I thought I'd ask since we're on a
Assuming it was all right with everyone, I'm setting the freeze date for 1.2.0 for
tomorrow (Saturday) night.
I'm updating the release plan. There are still a lot of enhancement patches that we
haven't applied, but I think those can wait for later in the 1.2.x series. I do intend
to start
At 9:37 AM -0500 2/20/04, Ted Husted wrote:
Assuming it was all right with everyone, I'm setting the freeze date
for 1.2.0 for tomorrow (Saturday) night.
I'm updating the release plan. There are still a lot of enhancement
patches that we haven't applied, but I think those can wait for
later in
On Fri, 20 Feb 2004, Ted Husted wrote:
Assuming it was all right with everyone, I'm setting the freeze date for 1.2.0 for
tomorrow (Saturday) night.
I'm updating the release plan. There are still a lot of enhancement patches that we
haven't applied, but I think those can wait for later in
--- Martin Cooper [EMAIL PROTECTED] wrote:
On Fri, 20 Feb 2004, Ted Husted wrote:
Assuming it was all right with everyone, I'm setting the freeze date
for 1.2.0 for tomorrow (Saturday) night.
I'm updating the release plan. There are still a lot of enhancement
patches that we haven't
contrib
Personally, I've been defining what is released by what is generated by the release
target. :)
For Struts 1.1, Struts-El was released coincident with the Struts 1.1 release, but
they were separate events. If someone wants to also roll a struts-el release, or
struts-jsf release,
Just a few things:
* What about the new Apache license? Technically, it doesn't need to
change if we release before March 1st, but we're mighty close to that,
so
perhaps we should switch now?
+1 from me too; wasn't someone offering to do it a few weeks ago?
At this point I don't see any
At 1:49 PM -0600 2/20/04, Joe Germuska wrote:
Just a few things:
* What about the new Apache license? Technically, it doesn't need to
change if we release before March 1st, but we're mighty close to that,
so
perhaps we should switch now?
+1 from me too; wasn't someone offering to do it a
.
-Original Message-
From: Joe Germuska [mailto:[EMAIL PROTECTED]
Sent: Friday, February 20, 2004 12:12 PM
To: Struts Developers List
Subject: Re: [VOTE] 1.2.0 Release Plan
At 1:49 PM -0600 2/20/04, Joe Germuska wrote:
Just a few things:
* What about the new Apache license? Technically
.
-Original Message-
From: Joe Germuska [mailto:[EMAIL PROTECTED]
Sent: Friday, February 20, 2004 12:12 PM
To: Struts Developers List
Subject: Re: [VOTE] 1.2.0 Release Plan
At 1:49 PM -0600 2/20/04, Joe Germuska wrote:
Just a few things:
* What about the new Apache license? Technically
: Re: [VOTE] 1.2.0 Release Plan
At 1:49 PM -0600 2/20/04, Joe Germuska wrote:
Just a few things:
* What about the new Apache license? Technically, it doesn't need
to change if we release before March 1st, but we're mighty close to
that, so
perhaps we should switch now?
+1
[mailto:[EMAIL PROTECTED]
Sent: Friday, February 20, 2004 12:12 PM
To: Struts Developers List
Subject: Re: [VOTE] 1.2.0 Release Plan
At 1:49 PM -0600 2/20/04, Joe Germuska wrote:
Just a few things:
* What about the new Apache license? Technically, it doesn't need
to change if we
On Wed, 24 Dec 2003, Joe Germuska wrote:
At 9:38 AM -0500 12/22/03, Robert Leland wrote:
I believe Joe said though all unit test ran they **didn't** all
pass, I believe it was like 66%
passed.
Hi, all... I've been at my in-laws for the holidays and have
intermittent net access.
I turned
At 9:38 AM -0500 12/22/03, Robert Leland wrote:
I believe Joe said though all unit test ran they **didn't** all
pass, I believe it was like 66%
passed.
Hi, all... I've been at my in-laws for the holidays and have
intermittent net access.
I turned out my major ant/cactus problem was that Ant
I haven't had a chance to catch up completely, but the outage this weekend
suggests an after-Christmas 1.2.0 release, unfortunately - at least, if I
need to be involved. (If not, great - go for it!)
--
Martin Cooper
On Sun, 21 Dec 2003, Ted Husted wrote:
OK, here's what we have
* Release
Ted Husted wrote:
OK, here's what we have
I would say release, we are using a x.y.z numbering scheme.
Noteing in the limited release that this should be considered an Alpha
until further testing says otherwise. Also to ask others not to announce
this on other lists
until it has been voted
Robert Leland wrote:
Ted Husted wrote:
OK, here's what we have
I would say release, we are using a x.y.z numbering scheme.
Noteing in the limited release that this should be considered an Alpha
until further testing says otherwise. Also to ask others not to announce
this on other lists
I am now testing nightly and sample wars for what it's worth.
All wars work (once over lightly).
Somone did a nice job on localizing validation war.
bP works (which uses jstl 1.1, struts menu 2.1, etc.)
-Validation example complains in console about formset not terminated
at end of file in
OK, here's what we have
* Release notes updated
* Issues w/o solutions marked LATER
* Webapps tested on TC 4.1 (one issue)
* JUnit tests run
In the Validator example, we're suppose to be able to change selected
validations for a county just by overriding a form in a formset. This
doesn't work
So, there were a few more outstanding reports that I thought we would have.
http://tinyurl.com/ysx3x
Six have patches, which I will try to apply tomorrow. Most of the others
are reports about problems I may not know how to fix.
I can thing of four ways to deal with these:
(1) mark reports
--- Ted Husted [EMAIL PROTECTED] wrote:
So, there were a few more outstanding reports that I thought we would
have.
http://tinyurl.com/ysx3x
Notice that 12 of the 29 bugs are custom tag related proving once again
how badly we need to move them into their own distro.
Six have patches,
+1
David
--- Ted Husted [EMAIL PROTECTED] wrote:
I've amended the date on the (now venerable) 1.2.0 release plan for this
weekend.
http://jakarta.apache.org/struts/proposals/release-plan_1_2_0.html
I believe the release notes are in good shape now. I already marched
through most of
Ted Husted wrote:
. If someone were up for sheparding the tests, especially the
example application testing,
If testing example apps, means not much more than see if the war files
work and browse it, I will do it. (of course some of them had problems
before, like tiles example, but not sure
+1
I've added myself as an RM, since I'll be available to help. I can take on
the tag, roll, sign and announce part, if you like.
One thing I'd like to point out, because it came up in Commons, is that
the HTTPD process and the Jakarta process are not 100% compatible. In
particular, the Jakarta
With this proposal, I took a middle ground. The initial minor release
(x.x.0) in a series called for a vote on a plan, but a plan would be
optional for additional releases in the same series (1.2.1, 1.2.2, ...).
So, we wouldn't have to vote on a plan again until we get to 1.3.0 or
2.0.0.
The
The issue isn't so much with voting on the relesae plan, but voting on the
release itself. As you say, the HTTPD rules say that anyone can create a
release. We're not HTTPD, though, and the Jakarta rules are different. As
long as we're part of Jakarta, we need to abide by the Jakarta rules.
Under
+1
-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 16, 2003 05:48 PM
To: 'Struts Developers List'
Subject: [VOTE] 1.2.0 Release Plan
I've amended the date on the (now venerable) 1.2.0 release plan for this
weekend.
Quoting Martin Cooper [EMAIL PROTECTED]:
The issue isn't so much with voting on the relesae plan, but voting on the
release itself. As you say, the HTTPD rules say that anyone can create a
release. We're not HTTPD, though, and the Jakarta rules are different. As
long as we're part of Jakarta,
Ok, then with 'tomcat' reading of the rules, I can put the 1.1.1
back for limited testing and then say next week call
for a vote on commons-validator to classify it.
I confused the issue by calling it an Alpha instead of
a RC.
-Rob
-Original Message-
From: Craig R. McClanahan Quoting
Were we still planning on using Validator 1.1.1 when it is released ?
It's getting a little confusing, since I removed it, and called
for a release Vote. The vote isn't scheduled to complete until
Sunday Noon. And Struts source will be frozed at Saturday Midnight.
-Rob
Clarifying the voting guidelines is an active thread on the PMC list, so
we might just want to muddle along best we can for now. Regardless of
what we do for 1.2.1, we have called for a vote on a release plan for
1.2.0. The plan does call for a vote before classifying the Alpha as a
Beta or
If we use the current Validator 1.1.1 JAR, and it becomes the final
release, then we could vote on whether Struts 1.2.0 can also be a
final or General Availability release.
If this Validator 1.1.1 JAR does not make final, then the best we could
do is mark ours would be beta (since it has a
--- Ted Husted [EMAIL PROTECTED] wrote:
The mean number of milestones for a Jakarta stable release seems to be
five or six. So, it would not be unusual for us to get 1.2.4 before
hitting a General Availability grade.
That could be because products using this versioning/release system don't
On Tue, 16 Dec 2003, Ted Husted wrote:
+1
I've amended the date on the (now venerable) 1.2.0 release plan for this
weekend.
http://jakarta.apache.org/struts/proposals/release-plan_1_2_0.html
I believe the release notes are in good shape now. I already marched
through most of the stale
+ 1 on the release plan...
Note that I've left room in the release plan for the idea of
multiple managers. If someone were up for sheparding the tests,
especially the example application testing, I'd welcome the help.
I may as well take this moment to fess up to my remedial status
trying to
Ted Husted wrote:
If we use the current Validator 1.1.1 JAR, and it becomes the final
release, then we could vote on whether Struts 1.2.0 can also be a
final or General Availability release.
If you recall I believe we came to consensus on struts-dev that
Validator can't go Beta or GA w/o being
45 matches
Mail list logo
