I created the release notes for the Struts 2.0.11 release. I'm not sure I did
it correctly though since 2.0.10 never saw the light of day. How do we
handle the scenario where this release is simply fixes to the previous release
that had all of the changes in it?
http://cwiki.apache.org/confluen
If that's the consensus, that's fine by me. I am proud our community has
worked so hard to have such a well-used long-lived project.
Congrats to everyone in our community.
Paul
On 9/19/07, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
>
> On Wed, September 19, 2007 10:46 am, Martin Cooper wrote:
On Wed, September 19, 2007 10:46 am, Martin Cooper wrote:
> On 9/19/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
>>
>> Ted,
>>
>> You can come up with the wording. I am not Mr. Prose :-) If you need
>> numbers, we have over 2500+ closed defects.
>
>
> Yeah, but that makes it sound like Struts was b
On 9/19/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
>
> Ted,
>
> You can come up with the wording. I am not Mr. Prose :-) If you need
> numbers, we have over 2500+ closed defects.
Yeah, but that makes it sound like Struts was buggy as hell, if we had that
many to "fix"...
--
Martin Cooper
Pau
Ted,
You can come up with the wording. I am not Mr. Prose :-) If you need
numbers, we have over 2500+ closed defects.
Paul
On 9/19/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
>
> 2007/9/19, Paul Benedict <[EMAIL PROTECTED]>:
> > Struts 1 just hit a historic marker. After 7 years of developme
2007/9/19, Paul Benedict <[EMAIL PROTECTED]>:
> Struts 1 just hit a historic marker. After 7 years of development, 90% of
> all reported issues are now closed.
Sincerely, I don't think that the open/closed ratio is a good
indicator, for a simple mathematical reason.
Closed issues accumulate over t
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 req
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 a
Oops. I lost a month being up at 2 AM. :-)
Please read Aug 17 to mean Sep 17 :)
Paul
On 9/19/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
>
> 2007/9/19, Paul Benedict <[EMAIL PROTECTED]>:
> > Version 2.3.1 was released yesterday (Aug 17).
>
> So you think we're still in august... :-)
>
>
2007/9/19, Paul Benedict <[EMAIL PROTECTED]>:
> Version 2.3.1 was released yesterday (Aug 17).
So you think we're still in august... :-)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTE
Good news if you need to generate TLD documentation for Maven!
Version 2.3.1 was released yesterday (Aug 17). This is the first new release
in over a year.
It contains an important bug fix for S1. Previous versions could not parse
embedded HTML in CDATA sections but instead escaped them (creating
1. Use JIRA search to find the tickets you want to modify. For instance,
maybe you want to find all unresolved 2.0.11 defects.
2. Then on the RHS above the search results there is a "bulk change" link.
Click that.
3. Check the tickets. You can also take all by selecting the checkbox in the
table
12 matches
Mail list logo
