Tapestry release numbering has flown in the face of Apache conventions for some time. It's time to change that.
What you should do is release a 4.1.1 release. Get it some exposure. Probably follow up with a 4.1.2 release. Eventually, we'll call a vote to "bless" a release as a stable 4.1 release. On 5/31/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
I'm wondering what the best course of action is in regard to: -) Release numbering - How do we want to handle this now? It's an alpha release, so should that language be made seperate from the official version name itself? -) When to release - How much API change can I get away with after making a release? Is saying it's alpha good enough to imply that people should code against it with care if something has to change? -) Code review / etc ? I think marketing is easy compared to all the other important stuff. I'd rather not have any articles come out about it until more widgets/functionality is easily visible. In its current form the system ~enables~ people to easily use ajax functionality, but is pretty sparse on actually providing concrete implementations. Would it be better to wait until more widgets/ajax stuff has been applied? -- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
-- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
