On Thu, Jun 22, 2006 at 08:36:47PM -0700, Paul Benedict wrote: > Well... What are the ramifications of removing bugzilla? Can we just > get rid of any bugzilla links we have on our site? Advertise jira.
A better solution would be to modify Bugzilla to let users know when a bug has been superceded. See: http://issues.apache.org/jira/browse/INFRA-859 --Jeff > Martin Cooper <[EMAIL PROTECTED]> wrote: On 6/22/06, Paul Benedict > wrote: > > > > What is the status of 1.3.5? It sounds like it's almost baked. > > > > By the way, I am volunteering to continue adding features to 1.x. Michael > > says he is also. I read today Niall is too. Who else on the team still > > wishes to add features for this codebase? Just looking to know who is on the > > "inner team". > > > I just switched employers, starting today, and my new employer is not > currently using Struts. If we do in the future, it's not likely to be 1.x. > That being the case, the likelihood of me putting my own time into 1.x is > somewhat low now. > > PS: Have you locked down Struts bugzilla? I saw someone last week entered a > > bug into it (I got a bugzilla mail), when they should have done so in JIRA. > > > Bugzilla can only be locked down for new bug entry, which has been done. > Unfortunately, there isn't a way to stop people updating existing issues, > which is somewhat annoying. ;-( > > -- > Martin Cooper > > > -- Paul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
