You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (JIRA)" <ji...@apache.org> on 2015/12/09 19:15:11 UTC
[jira] [Closed] (QPID-6755) Release tasks for qpid-java-6.0
[ https://issues.apache.org/jira/browse/QPID-6755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy closed QPID-6755.
----------------------------
Resolution: Done
> Release tasks for qpid-java-6.0
> -------------------------------
>
> Key: QPID-6755
> URL: https://issues.apache.org/jira/browse/QPID-6755
> Project: Qpid
> Issue Type: Bug
> Components: Documentation, Java Broker, Java Client, Java Common, Java Management : JMX Console, Java Performance Tests, Java Tests, Java Tools, JCA, Packaging, Website
> Reporter: Alex Rudyy
> Assignee: Alex Rudyy
> Fix For: qpid-java-6.0
>
>
> This JIRA is created to track the release activities for qpid-java-6.0.
> Here is the list of tasks I came so far to perform the release:
> # Ran RAT report and verify that all required files contain license header. Raise JIRA and resolve all unlicensed files.
> # Check JIRA for any remaining uncompleted JIRAs for qpid-java-6.0 and notify owners about closing the JIRAs before the release.
> # Send an email into dev list about release and tentative dates for alpha/beta/rc/release
> # Produce alpha and send an email about alpha availability for testing
> # Produce beta and send an email about beta availability for testing
> # Produce and sign RC and send an email about RC availability for testing
> ## Repeat above if blockers and critical issues requiring fixing are found
> # Initiate release voting by sending email into the dev list
> # Complete voting and when release is approved produce and sign final build
> # Publish release and update web site
> # Send a notification email about release availability
> The steps above are tentative. They could be changed or extended if required whilst performing the release activity.
> Publishing maven artifacts is covered in [here|http://www.apache.org/dev/publishing-maven-artifacts.html].
> Release signing is covered in [here|http://www.apache.org/dev/release-signing.html]
> It seems I need to set up pgp to sign the release. I need to do some research how to do that.
> Producing release artifacts with maven would require performing the following steps:
> # mvn release:prepare (updates versions, creates the branch, updates
> versions again)
> # mvn release:perform (performs release, publishing to Nexus staging area)
> # close Nexus staging repo
> # upload source release artifacts to svn dist dev repo (after downloading them from Nexus)
> # release Nexus staging repo (after voting)
> # add artifacts to svn dist release repo (after voting)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org