Looking at it further, this could all be done with JIRA how, which would probably be an easier interface to use and have
the bonus of collecting comments and patches. Perhaps we could use the "Priority" value to signify the type of issue
much like that status file does for httpd?
The WebWork team goes so far as using JIRA tickets for simple task management (assigning tickets, notifying the start of
work on a ticket, etc). Perhaps we should use that more, then have JIRA send a status summary to dev@ much like
Bugzilla does today. They also are strict about assigning tickets to milestones, like we've started to do. This will
help guide expectations on what will be in what release.
Don
Ted Husted wrote:
On 4/20/06, Don Brown <[EMAIL PROTECTED]> wrote:
The bottom line is, IMO, the Struts project hasn't been as good as it could
be at sharing our roadmap and vision with the user community. It is a
personal goal of mine to improve this, and to see the continued success of
both projects.
One habit that Apache HTTPD practices, that we never learned at
Jakarta, is the care and feeding of a STATUS file. Here's a link to
the current HTTPD status file, which they post to the dev@ on a
regular basis.
* http://svn.apache.org/repos/asf/httpd/httpd/trunk/STATUS
We do have a "starter" STATUS file in the SVN,
* http://svn.apache.org/repos/asf/struts/STATUS.txt
but if we want to get back to roadmap and communcation basics, I'd
suggest this is the place to start.
-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]
