I'm fine with combining the tasks as long as they are all resolved in one fell
swoop. Considering we generally have little spare time to work on open source
projects, I'd like to see tickets at a level of granularity that it only
requires a few hours to resolve them, avoiding the basically unresolvable
tickets like Struts Action 1 had ("Struts fails in too many places, etc).
Don
James Mitchell wrote:
Would you care if we use this ticket for all Struts projects? (Action
1.2.x, 1.3.x, 2.0.x, Shale, and Tiles)
Sean and I are meeting today for our mini hackathon and it might be a
good idea to keep all of these together.
--
James Mitchell
On Jun 14, 2006, at 7:29 AM, Ted Husted (JIRA) wrote:
Setup Nightly Builds of SAF2
----------------------------
Key: WW-1348
URL: http://issues.apache.org/struts/browse/WW-1348
Project: Struts Action 2
Type: Task
Components: Misc
Versions: 2.0.0
Reporter: Ted Husted
Priority: Critical
--This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
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]
