Shapira, Yoav wrote:
Hi, I (and others) have Bugzilla "Edit Components" karma and can help you. But there's already a Configuration component under the Commons product (using the Bugzilla terminology). The broader question is if we want to escalate/elevate commons projects into their own Bugzilla products -- I'd say probably not. If a project is ready for that, it's ready for promotion out the Commons first and into its own project (i.e. configuration.jakarta.org).
Well it's really not about pushing a project out of the Commons, it's just about using the tool the best way. Technically a commons project is not a Bugzilla component, that's why I make this request.
Some Apache projects use several Bugzilla projects for their needs, for example httpd, tomcat, cocoon and xerces. So, why not Jakarta Commons after all ? :)
I don't expect every commons project to move to a separate bugzilla project but those interested in such a move should be free to do it, just like migrating to Jira.
Emmanuel Bourg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
