<div dir="ltr">Hi guys,<div><br></div><div>+1 to Roman's suggestion.</div><div><br></div><div>I think we have to use 0.MINOR.PATCH at least during a few cycles.</div><div>API changes aren't a problem if we use a specific (frozen) version in requirements.</div>
<div><br></div><div>Thanks,</div><div>Igor</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 30, 2014 at 6:37 PM, Roman Podoliaka <span dir="ltr"><<a href="mailto:rpodolyaka@mirantis.com" target="_blank">rpodolyaka@mirantis.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Sergey,<br>
<br>
tl;dr<br>
<br>
I'd like to be a ready to use version, but not 1.0.0.<br>
<br>
So it's a good question and I'd like to hear more input on this from all.<br>
<br>
If we start from 1.0.0, this will mean that we'll be very limited in<br>
terms of changes to public API we can make without bumping the MAJOR<br>
part of the version number. I don't expect the number of those changes<br>
to be big, but I also don't want us to happen in a situation when we<br>
have oslo.db 3.0.0 in a few months (if we follow semver<br>
pragmatically).<br>
<br>
Perhaps, we should stick to 0.MINOR.PATCH versioning for now (as e.g.<br>
SQLAlchemy and TripleO projects do)? These won't be alphas, but rather<br>
ready to use versions. And we would still have a bit more 'freedom' to<br>
do small API changes bumping the MINOR part of the version number (we<br>
could also do intermediate releases deprecating some stuff, so we<br>
don't break people projects every time we make some API change).<br>
<br>
Thanks,<br>
Roman<br>
<div class="HOEnZb"><div class="h5"><br>
On Fri, May 30, 2014 at 6:06 PM, Sergey Lukjanov <<a href="mailto:slukjanov@mirantis.com">slukjanov@mirantis.com</a>> wrote:<br>
> Hey Roman,<br>
><br>
> will it be the alpha version that should not be used by other projects<br>
> or it'll be ready to use?<br>
><br>
> Thanks.<br>
><br>
> On Fri, May 30, 2014 at 6:36 PM, Roman Podoliaka<br>
> <<a href="mailto:rpodolyaka@mirantis.com">rpodolyaka@mirantis.com</a>> wrote:<br>
>> Hi Matt,<br>
>><br>
>> We're waiting for a few important fixes to be merged (usage of<br>
>> oslo.config, eventlet tpool support). Once those are merged, we'll cut<br>
>> the initial release.<br>
>><br>
>> Thanks,<br>
>> Roman<br>
>><br>
>> On Fri, May 30, 2014 at 5:19 PM, Matt Riedemann<br>
>> <<a href="mailto:mriedem@linux.vnet.ibm.com">mriedem@linux.vnet.ibm.com</a>> wrote:<br>
>>><br>
>>><br>
>>> On 4/25/2014 7:46 AM, Doug Hellmann wrote:<br>
>>>><br>
>>>> On Fri, Apr 25, 2014 at 8:33 AM, Matt Riedemann<br>
>>>> <<a href="mailto:mriedem@linux.vnet.ibm.com">mriedem@linux.vnet.ibm.com</a>> wrote:<br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> On 4/18/2014 1:18 PM, Doug Hellmann wrote:<br>
>>>>>><br>
>>>>>><br>
>>>>>> Nice work, Victor!<br>
>>>>>><br>
>>>>>> I left a few comments on the commits that were made after the original<br>
>>>>>> history was exported from the incubator. There were a couple of small<br>
>>>>>> things to address before importing the library, and a couple that can<br>
>>>>>> wait until we have the normal code review system. I'd say just add new<br>
>>>>>> commits to fix the issues, rather than trying to amend the existing<br>
>>>>>> commits.<br>
>>>>>><br>
>>>>>> We haven't really discussed how to communicate when we agree the new<br>
>>>>>> repository is ready to be imported, but it seems reasonable to use the<br>
>>>>>> patch in openstack-infra/config that will be used to do the import:<br>
>>>>>> <a href="https://review.openstack.org/#/c/78955/" target="_blank">https://review.openstack.org/#/c/78955/</a><br>
>>>>>><br>
>>>>>> Doug<br>
>>>>>><br>
>>>>>> On Fri, Apr 18, 2014 at 10:28 AM, Victor Sergeyev<br>
>>>>>> <<a href="mailto:vsergeyev@mirantis.com">vsergeyev@mirantis.com</a>> wrote:<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> Hello all,<br>
>>>>>>><br>
>>>>>>> During Icehouse release cycle our team has been working on splitting of<br>
>>>>>>> openstack common db code into a separate library blueprint [1]. At the<br>
>>>>>>> moment the issues, mentioned in this bp and [2] are solved and we are<br>
>>>>>>> moving<br>
>>>>>>> forward to graduation of oslo.db. You can find the new oslo.db code at<br>
>>>>>>> [3]<br>
>>>>>>><br>
>>>>>>> So, before moving forward, I want to ask Oslo team to review oslo.db<br>
>>>>>>> repository [3] and especially the commit, that allows the unit tests to<br>
>>>>>>> pass<br>
>>>>>>> [4].<br>
>>>>>>><br>
>>>>>>> Thanks,<br>
>>>>>>> Victor<br>
>>>>>>><br>
>>>>>>> [1] <a href="https://blueprints.launchpad.net/oslo/+spec/oslo-db-lib" target="_blank">https://blueprints.launchpad.net/oslo/+spec/oslo-db-lib</a><br>
>>>>>>> [2] <a href="https://wiki.openstack.org/wiki/Oslo/GraduationStatus#oslo.db" target="_blank">https://wiki.openstack.org/wiki/Oslo/GraduationStatus#oslo.db</a><br>
>>>>>>> [3] <a href="https://github.com/malor/oslo.db" target="_blank">https://github.com/malor/oslo.db</a><br>
>>>>>>> [4]<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> <a href="https://github.com/malor/oslo.db/commit/276f7570d7af4a7a62d0e1ffb4edf904cfbf0600" target="_blank">https://github.com/malor/oslo.db/commit/276f7570d7af4a7a62d0e1ffb4edf904cfbf0600</a><br>
>>>>>>><br>
>>>>>>> _______________________________________________<br>
>>>>>>> OpenStack-dev mailing list<br>
>>>>>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>>>><br>
>>>>>><br>
>>>>>> _______________________________________________<br>
>>>>>> OpenStack-dev mailing list<br>
>>>>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>>>><br>
>>>>><br>
>>>>> I'm probably just late to the party, but simple question: why is it in<br>
>>>>> the<br>
>>>>> malor group in github rather than the openstack group, like<br>
>>>>> oslo.messaging<br>
>>>>> and oslo.rootwrap? Is that temporary or will it be moved at some point?<br>
>>>><br>
>>>><br>
>>>> This is the copy of the code being prepared to import into a new<br>
>>>> oslo.db repository. It's easier to set up that temporary hosting on<br>
>>>> github. The repo has been approved to be imported, and after that<br>
>>>> happens it will be hosted on our git server like all of the other oslo<br>
>>>> libraries.<br>
>>>><br>
>>>> Doug<br>
>>>><br>
>>>>><br>
>>>>> --<br>
>>>>><br>
>>>>> Thanks,<br>
>>>>><br>
>>>>> Matt Riedemann<br>
>>>>><br>
>>>>><br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> OpenStack-dev mailing list<br>
>>>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> OpenStack-dev mailing list<br>
>>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>>><br>
>>><br>
>>> Are there any status updates on where we are with this [1]? I see that<br>
>>> oslo.db is in <a href="http://git.openstack.org" target="_blank">git.openstack.org</a> now [2]. There is a super-alpha dev package<br>
>>> on pypi [3], are we waiting for an official release?<br>
>>><br>
>>> I'd like to start moving nova over to using oslo.db or at least get an idea<br>
>>> for how much work it's going to be. I don't imagine it's going to be that<br>
>>> difficult since I think a lot of the oslo.db code originated in nova.<br>
>>><br>
>>> [1] <a href="https://review.openstack.org/#/c/91407/" target="_blank">https://review.openstack.org/#/c/91407/</a><br>
>>> [2] <a href="http://git.openstack.org/cgit/openstack/oslo.db/" target="_blank">http://git.openstack.org/cgit/openstack/oslo.db/</a><br>
>>> [3] <a href="https://pypi.python.org/pypi/oslo.db/0.0.1.dev15.g7efbf12" target="_blank">https://pypi.python.org/pypi/oslo.db/0.0.1.dev15.g7efbf12</a><br>
>>><br>
>>><br>
>>> --<br>
>>><br>
>>> Thanks,<br>
>>><br>
>>> Matt Riedemann<br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> OpenStack-dev mailing list<br>
>>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>> _______________________________________________<br>
>> OpenStack-dev mailing list<br>
>> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
> --<br>
> Sincerely yours,<br>
> Sergey Lukjanov<br>
> Sahara Technical Lead<br>
> (OpenStack Data Processing)<br>
> Principal Software Engineer<br>
> Mirantis Inc.<br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>