Several gerrit repositories have no tag 2014.1.3

Bug #1393928 reported by Timur Nurlygayanov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Undecided
Unassigned

Bug Description

We have many repositories for MOS 5.1.1 without tag 2014.1.3:

1) designate
https://review.fuel-infra.org/gitweb?p=openstack%2Fdesignate.git;a=shortlog;h=refs%2Fheads%2Fopenstack-ci%2Ffuel-5.1.1%2F2014.1.1

2) glance_store
https://review.fuel-infra.org/gitweb?p=openstack%2Fglance_store.git;a=shortlog;h=refs%2Fheads%2Fopenstack-ci%2Ffuel-5.1.1%2F2014.1.1

3) murano
https://review.fuel-infra.org/gitweb?p=openstack%2Fmurano.git;a=shortlog;h=refs%2Fheads%2Fopenstack-ci%2Ffuel-5.1.1%2F2014.1.1

4) murano-api
https://review.fuel-infra.org/gitweb?p=openstack%2Fmurano-api.git;a=shortlog;h=refs%2Fheads%2Fopenstack-ci%2Ffuel-5.1.1%2F2014.1.1

5) murano-apps
https://review.fuel-infra.org/gitweb?p=openstack%2Fmurano-apps.git;a=shortlog;h=refs%2Fheads%2Fopenstack-ci%2Ffuel-5.1.1%2F2014.1.1

6) murano-dashboard
https://review.fuel-infra.org/gitweb?p=openstack%2Fmurano-dashboard.git;a=shortlog;h=refs%2Fheads%2Fopenstack-ci%2Ffuel-5.1.1%2F2014.1.1

7) oslo (and all oslo* repositories)
https://review.fuel-infra.org/gitweb?p=openstack%2Foslo.git;a=shortlog;h=refs%2Fheads%2Fopenstack-ci%2Ffuel-5.1.1%2F2014.1.1

8) All python clients.
examples:
python-ceilometerclient
https://review.fuel-infra.org/gitweb?p=openstack%2Fpython-ceilometerclient.git;a=shortlog;h=refs%2Fheads%2Fopenstack-ci%2Ffuel-5.1.1%2F2014.1.1
python-cinderclient
https://review.fuel-infra.org/gitweb?p=openstack%2Fpython-cinderclient.git;a=shortlog;h=refs%2Fheads%2Fopenstack-ci%2Ffuel-5.1.1%2F2014.1.1
python-glanceclient
https://review.fuel-infra.org/gitweb?p=openstack%2Fpython-glanceclient.git;a=shortlog;h=refs%2Fheads%2Fopenstack-ci%2Ffuel-5.1.1%2F2014.1.1
python-heatclient
https://review.fuel-infra.org/gitweb?p=openstack%2Fpython-heatclient.git;a=shortlog;h=refs%2Fheads%2Fopenstack-ci%2Ffuel-5.1.1%2F2014.1.1

9) swift
https://review.fuel-infra.org/gitweb?p=openstack%2Fswift.git;a=shortlog;h=refs%2Fheads%2Fopenstack-ci%2Ffuel-5.1.1%2F2014.1.1

10) trove
https://review.fuel-infra.org/gitweb?p=openstack%2Ftrove.git;a=shortlog;h=refs%2Fheads%2Fopenstack-ci%2Ffuel-5.1.1%2F2014.1.1

Changed in fuel:
assignee: nobody → Fuel OSCI Team (fuel-osci)
importance: Undecided → High
milestone: none → 5.1.1
Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

Trove and Designate are irrelevant as we do not pack them into 5.1.1.

Swift does not follow general OpenStack rules and it does not have tags like 2014.1.3, instead it has linearly increasing version numbers like 2.1.0, 2.2.0, etc.

The same applies to oslo libraries and all python clients.

So, overall, it is expected that we don't have 2014.1.3 tag for the above repos. The only repos which are left under question are murano* and glance_store. I would like to ask Murano and Glance team members to comment on this.

Revision history for this message
Mike Scherbakov (mihgen) wrote :

Folks,
why it is assigned to OSCI team? I thought it's purely falls to mos-openstack team, which knows where should be tag. More over, when we get changes from upstream and merge into our branches, don't we have tag already there associated with one of the commits?

Revision history for this message
Dmitry Burmistrov (dburmistrov) wrote :

glance_store is Juno package. So it's only murano issues. Reassigned.

Changed in fuel:
assignee: Fuel OSCI Team (fuel-osci) → Murano Team (murano)
Revision history for this message
ruhe (ruhe) wrote :

Murano didn't follow OpenStack release naming conventions in Icehouse which is 2014.1.x. We started doing it in Juno (2014.2.x)
Swift doesn't follow this convention
Python clients have their own versioning scheme
oslo libraries have their own versioning scheme

trove and designate are not part of MOS, so, we don't care about them.

Changed in fuel:
status: New → Invalid
assignee: Murano Team (murano) → nobody
importance: High → Undecided
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.