Thanks, Paul. We dropped the ball on the issue tickets during the 1.1
deathmarch, and never really recovered. It's nice to see progress. Are
there really 35 open bug tickets against Struts 1, or are some of
these unreviewed and unconfirmed? At the point of a release, we
usually have zero open bug
Ted,
Are there really 35 open bug tickets against Struts 1, or are some of
these unreviewed and unconfirmed?
Where are you getting the 35 number from?
At the point of a release, we
usually have zero open bug tickets.
I still have a bunch of incremental improvements for Struts 1.3, and the
On 11/27/06, Paul Benedict [EMAIL PROTECTED] wrote:
Where are you getting the 35 number from?
*
https://issues.apache.org/struts/secure/IssueNavigator.jspa?mode=hiderequestId=10674
I still have a bunch of incremental improvements for Struts 1.3, and the
release of 1.3.6 is kind of
Ted Husted wrote:
*
https://issues.apache.org/struts/secure/IssueNavigator.jspa?mode=hiderequestId=10674
At least half of those are enhancement requests. I had every intention
of continuing to build these into 1.3.6 until your idea to do a release.
The others are unconfirmed bugs. If you
I cleaned up about 50 tickets inside of Struts 1. Mostly I :
* Moved tickets into their respective buckets that had no component
association (the association was easy to determine).
* Closed out tickets that were resolved by previous releases.
* Attached versions to the tickets.
It is looking
Is it easy to rename components? Under Struts Action 1, the component
'Action' should be 'Core'.
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Yep, you have admin access, so go ahead. Feel free to also create the Shale
project, and move its tickets over. :)
Don
Wendy Smoak wrote:
Is it easy to rename components? Under Struts Action 1, the component
'Action' should be 'Core'.
--
Wendy
Thanks to our Bugzilla import, we seem to have a bunch of issues, 182 to
be exact, that are resolved as Unresolved, but at a workflow state of
Closed or Resolved. Unfortunately, the bulk change feature only
lets you change the workflow state, not the Resolved field value.
This is
Hello, my name is Dave Evans, I've been lurking here for a while. I'd be
willing to do this, if its something that a non commiter can do.
dave
On Sun, 2006-04-23 at 23:43 -0700, Don Brown wrote:
Thanks to our Bugzilla import, we seem to have a bunch of issues, 182 to
be exact, that are
Yes, it is something a non-committer can do.
-Ted
On 4/24/06, David Evans [EMAIL PROTECTED] wrote:
Hello, my name is Dave Evans, I've been lurking here for a while. I'd be
willing to do this, if its something that a non commiter can do.
dave
On Sun, 2006-04-23 at 23:43 -0700, Don Brown
Ok. I just signed up for an account at http://issues.apache.org, and did
a search on status Closed and resolutions Unresolved. I see the 182
issues, in the issue details, i don't have the available workflow
actions section on the left. I signed up for a test account on
altassian's site, so i see
First, thanks for jumping in! I added you to the struts-developers
group, which should give you the appropriate access. As for the
changes, move Unresolved to Fixed.
Don
David Evans wrote:
Ok. I just signed up for an account at http://issues.apache.org, and did
a search on status Closed
No problem, glad to help. I've started, i did two tickets and was adding
comments:
http://issues.apache.org/struts/browse/STR-2749
Looking at the way these are displayed, it seems my comment isn't really
needed. Any preference one way or the other?
Dave
On Mon, 2006-04-24 at 07:56 -0700, Don
I wouldn't worry about, but it is up to you.
Don
David Evans wrote:
No problem, glad to help. I've started, i did two tickets and was adding
comments:
http://issues.apache.org/struts/browse/STR-2749
Looking at the way these are displayed, it seems my comment isn't really
needed. Any
14 matches
Mail list logo
