On Tue, Apr 4, 2017 at 9:36 PM, Emilien Macchi <emil...@redhat.com> wrote:
> adding [all] for more visibility... See comments inline:
>
> On Tue, Mar 21, 2017 at 2:02 PM, Emilien Macchi <emil...@redhat.com> wrote:
>> On Mon, Mar 13, 2017 at 12:29 PM, Alan Pevec <ape...@gmail.com> wrote:
>>> 2017-03-09 14:58 GMT+01:00 Jeremy Stanley <fu...@yuggoth.org>:
>>>> In the past we addressed this by automatically merging the release
>>>> tag back into master, but we stopped doing that a cycle ago because
>>>> it complicated release note generation.
>>>
>>> Also this was including RC >= 2 and final tags so as soon as the first
>>> stable maintenance version was released, master was again lower
>>> version.
>>
>> topic sounds staled.
>> Alan,  do we have an ETA on the RDO workaround?
>
> Without progress on RDO tooling and the difficulty of implementing it,
> I went ahead and proposed a semver bump for some projects:
>
> https://review.openstack.org/#/q/topic:sem-ver/pike
>
> Except for Swift where I don't know if they'll bump X, I proposed to bump Y.
> For all other projects, I bumped X as they did from Newton to Ocata.
> (where version is X.Y.Z).
>
> Please give any feedback on the reviews if you prefer another kind of bump.
> Thanks for reviewing that asap, so TripleO CI can test upgrades from
> Ocata to Pike soon.
>
> Thanks,

I forgot to mention that I didn't update Oslo yet, because I have no
clue which type of bump would be the best now.
Please use this url for review:
https://review.openstack.org/#/q/topic:sem-ver/pike+status:open

Thanks,

>> Thanks,
>>
>>> Cheers,
>>> Alan
>>>
>>> __________________________________________________________________________
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>> --
>> Emilien Macchi
>
>
>
> --
> Emilien Macchi



-- 
Emilien Macchi

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to