On 2 February 2018 at 17:54, Mark Thomas <ma...@apache.org> wrote: > Hello all, > > I propose that we create a new component [commons-signing]. > > The scope of the component is code signing utilities including, but not > limited to, Ant and Maven plugins for the Symantec code signing service that > a number of ASF projects use. > > We'll work most things out as we go along but the rough plan at this stage > is: > > * git repo > * start with the Symantec Ant task in Tomcat > * add the Maven plugin from Sling > * refactor out the duplicate code > * first release > > I'm leaning towards using GitHub issues rather than Jira.
I think this may be too basic. AFAIK it's currently not possible to document version numbers etc. It may be possible to add labels (Bug, Enhancement etc) but it does not look like it's possible to add a priority Also there are only two states: open and closed. It might be possible to use labels for some other states. There does not seem to be any history for changes to labels. In my experience GH issues work fine if there are not very many open ones. Otherwise it can get very unwieldy. > Please review the proposal and vote. This vote will close no sooner that 72 > hours from now. > > [X] +1 Create the component > [ ] +0 OK, but... > [ ] -0 OK, but really should fix... > [ ] -1 I oppose this component because… > > Cheers, > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
