Hi, This is a proposal to make a bit more scalable our JIRA and also to remove non direct Apache NetBeans related issue in the current JIRA NETBEANS. I think we can selfserve only for officer or member. But it's possible to have more than one jira project for NetBeans.
As mavenutilities and html4 are maven build its easy to have jira project to prepare release note than component, and also they have different versioning scheme than NetBeans I would like to propose the following: First create a Project category as JIRA NETBEANS is still seeing under Incubator category, Assign NetBeans to NetBeans Category, and use the url https://netbeans.apache.org as URL for all Upcase key is for project name within jira (I guess It's limited to 10 char) NetBeans Website, NBWEBSITE (component could be like that: -- website -- tutorial -- update center -- maven repo -- apidoc ... Tools ant based at version 3.0 NetBeans Jackpot, NBJACKPOT -- maven based more easy to manage release version on their own projects NetBeans Parent, NBPARENT NetBeans HTML4j, NBHTML4J -- maven based and mavenutilities NetBeans Mavenutilities Parent, NBMUPARENT NetBeans Mavenutilities Harness, NBMUHARNESS NetBeans Mavenutilities NBM Maven Plugin , NBMUPLUGIN NetBeans Mavenutilities NB Repository Plugin, NBMUREPO NetBeans Mavenutilities Shared lib, NBMUSHARED Hope it make sense Best Regards Eric --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
