[
https://issues.apache.org/jira/browse/MESOS-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kone updated MESOS-684:
-----------------------------
Description: Currently, when we tag a release candidate, we never upload
the relevant python artifacts (e.g., mesos egg) for the community to be able to
test it. It would be great if we can have a script to automate this. (was:
Currently, when we tag a release candidate, we never upload the relevant
artifacts (e.g., mesos jar) for the community to be able to test it. It would
be great if we can have a script to automate this.
Since we also support Python, we could (should?) also publish a mesos egg to
somewhere in Apache?)
Fix Version/s: (was: 0.16.0)
0.17.0
Summary: Automate publishing of python artifacts with release
candidates and releases (was: Automate publishing of artifacts with release
candidates and releases)
Updated the title and description to make this ticket specific to publishing
python artifacts.
Publishing of the jar and source distribution is being tracked at
https://issues.apache.org/jira/browse/MESOS-756.
> Automate publishing of python artifacts with release candidates and releases
> ----------------------------------------------------------------------------
>
> Key: MESOS-684
> URL: https://issues.apache.org/jira/browse/MESOS-684
> Project: Mesos
> Issue Type: Sub-task
> Reporter: Vinod Kone
> Fix For: 0.17.0
>
>
> Currently, when we tag a release candidate, we never upload the relevant
> python artifacts (e.g., mesos egg) for the community to be able to test it.
> It would be great if we can have a script to automate this.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
