Open Stack

Thanks Doug, Thierry and Davanum. Sorry about the all the extra work that I've caused.

It sounds like all Python projects/deliverables are in reasonable shape, but if not, please let me know. 

Not sure what we should do about the jars at this point. We had started to discuss a plan to manually copy the jars over to the proper location. I was hoping we could just do this temporarily for Mitaka. Unfortunately, there are a few steps that need to be resolved prior to doing that.

Currently, the java builds overwrite the previous build. The version number of the jar that is built, matches the version in the pom file. See, http://tarballs.openstack.org/ci/monasca-thresh/, for an example.

What we are looking into is modifying the pom files for the java repos, so that the version number of the jar matches the tag when built (not what is in the pom), and modifying the name of the jar, by removing the word SNAPSHOT.

If we do that, we think we can get a name for the jar with a version that matches the latest tag on whatever branch is being used. This should be similar to how the Python wheels that are named.

We could manually copy in the short-term. But the goal is to add an automatic copy to the appropriate location in, http://tarballs.openstack.org/.

Unfortunately, for the java related deliverables, it sounds like we are a little late for all this to get done prior to Mitaka. Not sure if this can be added post Mitaka.

Regards --Roland



On 4/5/16, 3:15 AM, "Thierry Carrez" <thierry at openstack.org> wrote:

>Davanum Srinivas wrote:
>> Please see below:
>>
>> On Sat, Apr 2, 2016 at 8:41 AM, Doug Hellmann <doug at doughellmann.com> wrote:
>>> Excerpts from Hochmuth, Roland M's message of 2016-04-02 01:35:35 +0000:
>>>> Hi Doug, You had mentioned issues with three repos:
>>>>
>>>> 1. monasca-ceilometer
>>>> 2. monasca-log-api
>>>> 3. monasca-thresh
>>>>
>>>> All the repos that have Python code I believe are in reasonable shape with respect to the Python deliverables except for the following two repos:
>>>>
>>>> 1. monasca-ceilometer
>>>> 2. monasca-log-api
>>>>
>>>> I'm not sure we should attempt to resolve these two repos for the Mitaka release, but we can try. It might be too late. They aren't in heavy usage and are relatively new.
>>>
>>> I think for those you were missing the "venv" environment in tox.ini
>>> that the jobs use to run arbitrary commands. Have a look at some of the
>>> other repos for an example of how to set that up, or ask the infra team
>>> (I'm not sure where it's documented, unfortunately, or I would direct
>>> you there).
>>
>> The monasca-log-api venv problem has been fixed in:
>> https://review.openstack.org/#/c/299936/
>
>Thanks dims!
>
>Roland: Now we'll need a 0.0.3 tag request on stable/mitaka to trigger a 
>tarball rebuild.
>
>If done quickly, that should let us keep Monasca deliverables in Mitaka.
>
>-- 
>Thierry Carrez (ttx)
>
>__________________________________________________________________________
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev