[
https://issues.apache.org/jira/browse/PROTON-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Harvey reassigned PROTON-210:
------------------------------------
Assignee: Rafael H. Schloming (was: Philip Harvey)
This has been committed to branch
https://svn.apache.org/repos/asf/qpid/proton/branches/jni-binding and will be
merged to trunk shortly.
I documented how I tested the script on the wiki, so that we can reuse these
steps in the future:
https://cwiki.apache.org/confluence/display/qpid/Proton+Release+Steps
I don't feel confident that I understand all the requirements of the tarball so
please could you take a look, and also review/update the wiki as appropriate.
I've left this Jira "In Progress" because I'm sure there'll be some further
tweaks required following your review.
Thanks for your help,
Phil
> Proton release.sh should create a single release tarball for proton-c/proton-j
> ------------------------------------------------------------------------------
>
> Key: PROTON-210
> URL: https://issues.apache.org/jira/browse/PROTON-210
> Project: Qpid Proton
> Issue Type: New Feature
> Components: proton-c, proton-j
> Reporter: Keith Wall
> Assignee: Rafael H. Schloming
>
> Following changes made by PROTON-194, the release script must change to
> create a single tarball containing proton-c, proton-j and test trees.
> The tarball should exclude proton-c/examples/mailbox and proton-j/contrib.
> It should contain to perform a maven the maven version set/commit.
> The ruby gem will be unaffected by this change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
