James, are there any specific tickets that are a direct impediment to a
1.3 release, as opposed to those things that could be dealt with
post-release?
Identifying those might help focus effort, especially if there are
non-commiters that might like to help but aren't sure exactly how best
to do so (with the specific goal of working towards a release I mean).
Frank
James Mitchell wrote:
I think it is high time we get something out there for 1.3, even if it
never makes it past beta, at least we are moving.
I'm about to head out on a working-vacation, and while I'm gone, I'll
try to get the release plan put together. Does anyone have any time
they'd like to donate in a week or so to help with this?
--
James Mitchell
Software Engineer / Open Source Evangelist
Consulting / Mentoring / Freelance
EdgeTech, Inc.
http://www.edgetechservices.net/
678.910.8017
AIM: jmitchtx
MSN: [EMAIL PROTECTED]
Skype: jmitchtx
----- Original Message ----- From: "netsql" <[EMAIL PROTECTED]>
To: <user@struts.apache.org>
Sent: Thursday, July 14, 2005 7:27 PM
Subject: Re: Struts 1.2 v 1.3
[EMAIL PROTECTED] wrote:
Ted, is there a list of tasks for 1.3? By "volunteer", are you
referring only to current Struts committers?
Anyone can edit / search bugzila.
Anyone can post a "diff" to code. Only a comiter can ... comit code.
(you become a comiter when comiters get tired of comiting your code)
.V
Erik
-----Original Message-----
From: Ted Husted <[EMAIL PROTECTED]>
Sent: Jul 14, 2005 6:57 PM
To: Struts Users Mailing List <user@struts.apache.org>
Subject: Re: Struts 1.2 v 1.3
On 7/14/05, Access Denied <[EMAIL PROTECTED]> wrote:
I just bought and am reading James Holmes' book, "Struts: The Complete
Reference" (Osborne 2004), which covers 1.2. I just learned from one
of Ted Husted's posts that 1.3 is almost ready to be released. Am I
wasting my time and should be studying other literature?
Hmmm, I may have said "almost", but I did not mean to imply "soon".
Right now, no one seems to be trying to push 1.3 out the door. There
is not even a release plan. The only timeframe for 1.3 is
"indefinate". It could be a week, or a month, or five months. It all
depends when a volunteer can step up to the plate.
Of course, should "indefinate" happen, it would not make any 1.2
material obsolete. By "1.3", we mean the release would be backwardly
compatible with 1.2.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
