On Sep 10, 2014, at 5:20 PM, Brant Knudson <b...@acm.org> wrote: > > > On Tue, Sep 9, 2014 at 4:19 PM, Sean Dague <s...@dague.net> wrote: > As we try to stabilize OpenStack Juno, many server projects need to get > out final client releases that expose new features of their servers. > While this seems like not a big deal, each of these clients releases > ends up having possibly destabilizing impacts on the OpenStack whole (as > the clients do double duty in cross communicating between services). > > As such in the release meeting today it was agreed clients should have > their final release by Sept 18th. We'll start applying the dependency > freeze to oslo and clients shortly after that, all other requirements > should be frozen at this point unless there is a high priority bug > around them. > > -Sean > > For the final client release, should they have their requirements updated to > the final release of the oslo libraries that they use? For example, > python-keystoneclient currently has oslo.config>=126.96.36.199a3. Seems like the > final client release should have the final oslo library in the requirements. > If so we'll need the final release of oslo.config, updated global > requirements, sync that to keystoneclient & merged before we can do the final > release of python-keystoneclient.
Good point. Yes, I think that’s a good idea. Maybe we should plan for the 19th for the clients to give time for all of those changes to land? We can make one requirements patch, after the oslo libs are all cut. Doug > > - Brant > > _______________________________________________ > OpenStack-dev mailing list > OpenStackemail@example.com > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev