We might want to clarify that we *always* resolve *all* bug reports
with a known fix. It's the feature requests where we fall behind,
especially those without patches.

And, of course, we always close all tickets against a particular
version before releasing it (which often means moving feature requests
to a future release.)

It does sound like it would be a record for S1 over the last four
years. (Thanks for cleaning these up!) Though, in the beginning, we
were able to keep the lid on the reported issues, so it's hard to tell
if it's historic over all seven years. Back in the day, we were
probably hitting 100%. The reported issues bulked up during the Struts
1.1 death march, when we fell behind on the feature requests (many of
which overlapped).

We'd have to be careful with the wording, since something like this is
easy to spin the other way. According to JIRA, 85% of Tapestry's and
Wickets issues are closed, Spring 2 is at 82%, and Hibernate 3 is at
67%.

 * http://issues.apache.org/jira/browse/TAPESTRY
 * http://issues.apache.org/jira/browse/WICKET
 * 
http://opensource.atlassian.com/projects/spring/browse/SPR?report=com.atlassian.jira.plugin.system.project:openissues-panel

So, we might want to mention something about many open source projects
have over 80% of issues closed at any time, and Struts is creeping
past 90%.

One concern would be that if we start focusing too much on open
tickets, people might think twice before opening a new ticket, and I
don't know if that's a good thing or not.

-Ted.


On 9/19/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
> Friends,
>
> Struts 1 just hit a historic marker. After 7 years of development, 90% of
> all reported issues are now closed. With the forthcoming 1.3.x and
> 1.4releases, it appears this will be bumped to 95% by middle 2008.
> Great news
> for everyone on our team!
>
> Would anyone mind if we added this little announcement on the website?
>
> Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to