You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Jake Farrell (JIRA)" <ji...@apache.org> on 2013/12/27 19:29:50 UTC
[jira] [Commented] (MESOS-684) Automate publishing of artifacts
with release candidates and releases
[ https://issues.apache.org/jira/browse/MESOS-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13857615#comment-13857615 ]
Jake Farrell commented on MESOS-684:
------------------------------------
As part of the Apache Thrift release process I include the sdist and eggs in the content for voting and then I upload the sdist to pypi after passing the vote (same for ruby client, etc). Have been looking at the Apache Mesos python scripts and trying to come up with a good way to handle this for Apache Aurora as this is currently a dependency and impacting testing. I am happy to help in this area and if needed publish the Apache Mesos egg or some form of sdist to pypi
> Automate publishing of 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.16.0
>
>
> 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?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)