Re: [PROPOSAL] Struts infrastructure changes

2004-03-21 Thread Jeff Turner
On Sat, Mar 20, 2004 at 09:44:23AM -0800, David Graham wrote: ... I've expressed my opposition to this on commons-dev so I'll sum up my points here: ... 2. We've been fairly consistent with tracking corresponding bugzilla bug numbers in the cvs commit messages. This has proved extremely

Re: [PROPOSAL] Struts infrastructure changes: Jira

2004-03-20 Thread Mike Kienenberger
Martin Cooper [EMAIL PROTECTED] wrote: Optional: Move to Jira (IMO, now's as good a time as any.) One thing I've noticed about Jira is that attachments cannot be deleted general developers, only members of the Jira admin group. Not sure if that's an issue. As a general user, I've found Jira

Re: [PROPOSAL] Struts infrastructure changes: Jira

2004-03-20 Thread Martin Cooper
On Sat, 20 Mar 2004, Mike Kienenberger wrote: Martin Cooper [EMAIL PROTECTED] wrote: Optional: Move to Jira (IMO, now's as good a time as any.) One thing I've noticed about Jira is that attachments cannot be deleted general developers, only members of the Jira admin group. Not sure if

Re: [PROPOSAL] Struts infrastructure changes

2004-03-20 Thread David Graham
--- Martin Cooper [EMAIL PROTECTED] wrote: The following is a set of proposed changes to the Apache infrastructure to accommodate the Struts move to an Apache top level project. The idea is to come up with a single agreed-upon set of changes that we can submit to the infrastructure folks

RE: [PROPOSAL] Struts infrastructure changes

2004-03-20 Thread Steve Raeburn
All sound good with the following comments: 1. CVS integrates very nicely with my IDE right now (Eclipse/WSAD). I don't know how well Subversion would integrate and I'd not want to move if I lost that integration. I'm sure that also applies to other IDEs. 2. Bugzilla/Jira make no difference to

Re: [PROPOSAL] Struts infrastructure changes

2004-03-20 Thread Ted Husted
I'm good with any of this, or with any product changes others want, or do not want, to make. :) On Sat, 20 Mar 2004 09:05:02 -0800 (PST), Martin Cooper wrote: The following is a set of proposed changes to the Apache infrastructure to accommodate the Struts move to an Apache top level project.

Re: [PROPOSAL] Struts infrastructure changes

2004-03-20 Thread Martin Cooper
On Sat, 20 Mar 2004, Martin Cooper wrote: The following is a set of proposed changes to the Apache infrastructure to accommodate the Struts move to an Apache top level project. The idea is to come up with a single agreed-upon set of changes that we can submit to the infrastructure folks as a

Re: [PROPOSAL] Struts infrastructure changes

2004-03-20 Thread Ted Husted
On Sat, 20 Mar 2004 15:59:15 -0800 (PST), Martin Cooper wrote: Do we want our own announcements@ list? In the past, we've sent release announcements to the Jakarta announcements list, so I'm wondering if we want one of our own now, for people who don't want to subscribe to the Struts -user or

Re: [PROPOSAL] Struts infrastructure changes

2004-03-20 Thread Craig R. McClanahan
Miscellaneous comments intermixed. Quoting Martin Cooper [EMAIL PROTECTED]: The following is a set of proposed changes to the Apache infrastructure to accommodate the Struts move to an Apache top level project. The idea is to come up with a single agreed-upon set of changes that we can submit

Re: [PROPOSAL] Struts infrastructure changes

2004-03-20 Thread Martin Cooper
On Sat, 20 Mar 2004, Craig R. McClanahan wrote: Miscellaneous comments intermixed. Quoting Martin Cooper [EMAIL PROTECTED]: The following is a set of proposed changes to the Apache infrastructure to accommodate the Struts move to an Apache top level project. The idea is to come up with