I am -1 for moving Jakarta Commons as a --whole-- to JIRA, If each sub-project of commons wants to move then thats ok. Why: There has been a Buzilla 2.16.4 available for some time that fixes several serious security issues. However, we haven't upgraded to that version, or any of the other improved versions, that have come around over the last 2 years. Does infrastructure really want to support 2 bug tracking systems ? I believe that the question of a BugTracking system to use is really an Apache wide decision, since if all projects don't move to JIRA, then there is 2 systems to maintain and learn. Are the JIRA people willing to provide admin type maintance for free ?
The biggest improvement would be to treat each commons sub-project, as a project in bugzilla. <strong>I also think that each committer should automatically be made a buzilla admin.</strong> As echoed by others I believe we should use OSS software where there is a viable alternative, with similar functionality. > -----Original Message----- > From: Noel J. Bergman [mailto:[EMAIL PROTECTED] > Sent: Monday, January 12, 2004 10:48 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [PROPOSAL] Jakarta Commons moving to JIRA > > Guys, > > There are separate requests on the table to move BETWIXT, CLI, CODEC, JEXL > and CONFIGURATION from Bugzilla to JIRA. JELLY is already there. > > Are there any other Jakarta Commons projects that want to migrate? Are > there any that do NOT want to leave bugzilla? > > Right now, each "project" is a component of Commons. If we move to JIRA, I > would propose that we create a Project Category for Jakarta Commons, and > make each component a project, so that each one can be released separately > with its own versioning, etc. We could use a common scheme for permissions, > notifications, etc.. Jelly has a dedicate scheme, but I think we could use > a single scheme for all of Jakarta Commons. > > A bugzilla import will create a single Commons project, but we can then move > the issues from the imported project into a new project for each of our real > projects. > > For each TLP, we should probably have a single permission scheme, but I'm > not going to get into that argument today. We can create > jakarta-administrator and jakarta-commons-developer groups. > > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
