[
http://jira.codehaus.org/browse/MJS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259603#action_259603
]
Anders Hammar commented on MJS-37:
----------------------------------
Why don't we, as Robert pointed out earlier, follow our release docs and start
with a vote on graduating this plugin from the sandbox? Then, the next step is
to do a release.
Or, could the project be kept as a sandbox project but still make a release?
Our release docs is a little bit vague on this I think, but I'm having a hard
time seeing that a sandbox project could make a 1.0 release. Quoting from the
release docs:
bq. If the plugin is making its first official release, it should graduate from
the sandbox.
What's an official release? Are there unofficial releases? Or do we simply mean
a release?
> 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
