[ https://jira.jboss.org/jira/browse/JBOSGI-176?page=com.atlassian.jira.plu... ] Thomas Diesler updated JBOSGI-176: ---------------------------------- Description: Here is the list of required steps to do a release * Copy the release notes from the Jira Roadmap to ChageLog.html * Extract the relevant changes to ReleaseNotes.html * Create the SVN tag (i.e. jboss-osgi-1.0.0) * Checkout the newly create tag and run 'mvn -Pdistro deploy' * Make the release on SourceForge * Create a news wiki page and link it to the news section * Blog about the release on JBossOSGi Diary (http://jbossosgi.blogspot.com) * Advertise the release on mailing lists (i.e. jboss-development(a)lists.jboss.org, thecore(a)jboss.org) The release procedure is documented here http://www.jboss.org/community/wiki/ReleaseProcedure was: Here is the list of required steps to do a release * Copy the release notes from the Jira Roadmap to ChageLog.html * Extract the relevant changes to ReleaseNotes.html * Create the SVN tag (i.e. jboss-osgi-1.0.0) * Checkout the newly create tag and run 'mvn -Pdistro deploy' * Make the release on SourceForge * Create a news wiki page and link it to the news section * Blog about the release on JBossOSGi Diary (http://jbossosgi.blogspot.com) * Advertise the release on mailing lists (i.e. jboss-development(a)lists.jboss.org, thecore(a)jboss.org) http://www.jboss.org/community/wiki/ReleaseProcedure -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBOSGI-176?page=com.atlassian.jira.plu... ] Thomas Diesler updated JBOSGI-176: ---------------------------------- Description: Here is the list of required steps to do a release * Copy the release notes from the Jira Roadmap to ChageLog.html * Extract the relevant changes to ReleaseNotes.html * Create the SVN tag (see http://maven.apache.org/plugins/maven-release-plugin) * Checkout the newly create tag and run 'mvn -Pdistro deploy' * Make the release on SourceForge * Create a news wiki page and link it to the news section * Blog about the release on JBossOSGi Diary (http://jbossosgi.blogspot.com) * Advertise the release on mailing lists (i.e. jboss-development(a)lists.jboss.org, thecore(a)jboss.org) The release procedure is documented here http://www.jboss.org/community/wiki/ReleaseProcedure was: Here is the list of required steps to do a release * Copy the release notes from the Jira Roadmap to ChageLog.html * Extract the relevant changes to ReleaseNotes.html * Create the SVN tag (i.e. jboss-osgi-1.0.0) * Checkout the newly create tag and run 'mvn -Pdistro deploy' * Make the release on SourceForge * Create a news wiki page and link it to the news section * Blog about the release on JBossOSGi Diary (http://jbossosgi.blogspot.com) * Advertise the release on mailing lists (i.e. jboss-development(a)lists.jboss.org, thecore(a)jboss.org) The release procedure is documented here http://www.jboss.org/community/wiki/ReleaseProcedure -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBOSGI-176?page=com.atlassian.jira.plu... ] Thomas Diesler resolved JBOSGI-176. ----------------------------------- Resolution: Done Done http://www.jboss.org/community/wiki/JBossOSGi100Beta4Released14-Oct-2009 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira