> [X] +1 - merge Jakarta Taglibs Project into this new project > [ ] -1 - no, let's keep Jakarta Taglibs Project as is > [ ] -1 - let's wait the new project be officially created/incubated > [ ] +0 - whatever > [ ] ?? - <<put your comment here>>
> 1.Jakarta Standard Taglibs should be a project of its own, given the > fact that it produces standard, JCP-compliant taglibs and as such have > peculiar characteristics. > > [X] +1 let's create a new project for these taglibs > [ ] -1 please, leave it with us wherever we go > [ ] -0 dude, the +1 didn't win the first vote, so we are not merging > [ ] ?? - <<put your comment here>> > 2.What about the other taglibs? Should we migrate them as is to the > new project or should we leave them behind and create new taglibs from > scratch (reusing existing code, of course)? > > 2.1 [ ] migrate all of them > 2.2 [X] leave them behind (on a read-only SVN access, with the latest > releases, etc..) and let's create new ones from scratch - that would > give us a chance to refactor the existing code. > 2.3 [ ] it's too early to decide that > 2.? [ ] <<put your comment here>> > 2.2.1 Last releases > > [X] +1 release a final version for each existing taglib (and a 1.0 for > those never released) before "closing the doors" > [ ] -1 no, leave them as is - we better do the new releases in the new > projects > [ ] ?? - explain why Abey Mullassery http://www.mullassery.com -------------------------------------------------------------------- mail2web - Check your email from the web at http://mail2web.com/ . --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
