[
http://jira.codehaus.org/browse/MJS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259291#action_259291
]
nicolas de loof commented on MJS-37:
------------------------------------
I'm not in favor of suffixing our releases with -beta-x and following.
We allready have many plugins that released multiple betas and never reach the
"final" step. This will not stop user to have expectation anyway
I'd prefer to get a 1.0 and maybe have a 2.0 if we plan some major refactoring
and incompatible changes in the plugin. Regarding a javascript-suite, we could
also have a distinct artifactId and deprecate the plugin if necessary
> Prepare the 1.0 release
> -----------------------
>
> Key: MJS-37
> URL: http://jira.codehaus.org/browse/MJS-37
> Project: Maven Javascript Tools
> Issue Type: Task
> Reporter: Tim Astle
> Assignee: Tim Astle
> Fix For: 1.0
>
>
> Prepare a 1.0 release of this plugin since there are so many nice people out
> there using this, and they deserve a release.
> Following the procedure outlined here:
> http://mojo.codehaus.org/development/performing-a-release.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
