This makes perfect sense to me John. But consistency across the project would be a nice-to-have for those who design and communicate the platform to decision makers who don't understand why they're signing off v1 of this, v2 of that, v1 of this other one... It portrays a sense of program incongruity (perceived or otherwise) which adds to existing concerns about platform complexity. I spend more time explaining why than otherwise.
Logical versioning vs "Nice to have". ; ) *Adam Lawson* AQORN, Inc. 427 North Tatnall Street Ste. 58461 Wilmington, Delaware 19801-2230 Toll-free: (844) 4-AQORN-NOW ext. 702 Int'l: +1-302-268-6914 ext. 702 Cell: +1-916-990-1226 On Tue, Jul 22, 2014 at 10:46 AM, Shrinand Javadekar < shrin...@maginatics.com> wrote: > > Hope this helps clear things up. > > This does. Thanks for the detailed explanation. > > -Shri > > > > > --John > > > > > > > > > > > > > > On Jul 22, 2014, at 10:05 AM, Shrinand Javadekar < > shrin...@maginatics.com> wrote: > > > >> This is confusing. So does this mean semantic versioning applies to > >> the API's and not the Swift product versions? If so how are the > >> product versions decided? And given a product version, how does one > >> know about what API version is in use? The /info endpoint does not > >> mention the API version. > >> > >> I had asked about versioning sometime ago [1] and I thought the > >> release version and API version are identical. > >> > >> -Shri > >> > >> [1] http://www.gossamer-threads.com/lists/openstack/dev/36042 > >> > >> > >> On Tue, Jul 22, 2014 at 5:37 AM, Anne Gentle <a...@openstack.org> > wrote: > >>> Hi Shri, > >>> The Object Storage API change is just to add a header called > >>> 'X-Storage-Policy: <name>' where name is set in the swift configuration > >>> files by the cloud provider. > >>> > >>> See http://docs.openstack.org/developer/swift/overview_policies.html > >>> > >>> We'll add it to the API docs next, no version change needed for the API > >>> itself. > >>> Anne > >>> > >>> > >>> On Tue, Jul 22, 2014 at 12:46 AM, Shrinand Javadekar > >>> <shrin...@maginatics.com> wrote: > >>>> > >>>> Hi, > >>>> > >>>> Swift has been following the semantic versioning scheme. The fact that > >>>> the product version changed from v1.x to v2.0 should suggest that the > >>>> Swift APIs changed in this release. > >>>> > >>>> I see that storage policies has been the biggest change in this > >>>> release. Has that impacted the APIs? > >>>> > >>>> Is there a document that lists exactly the API difference between > v1.x and > >>>> v2.0? > >>>> > >>>> Thanks in advance. > >>>> -Shri > >>>> > >>>> _______________________________________________ > >>>> Mailing list: > >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >>>> Post to : openstack@lists.openstack.org > >>>> Unsubscribe : > >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >>> > >>> > >> > >> _______________________________________________ > >> Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >> Post to : openstack@lists.openstack.org > >> Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
