Lets use https://etherpad.openstack.org/p/Icehouse-nova-oslo-sync to keep track of things.
On Wed, Feb 26, 2014 at 5:10 PM, Joe Gordon <joe.gord...@gmail.com> wrote: > GCB, Ben, > > Thanks for volunteering to help. > > GCB, reminded me that we should be doing this for python-novaclient in > addition to nova itself. So that being said, as I see it here are the > steps moving forward: > > Note: as previously mentionedin this thread there already is a team > working on syncing oslo.db so we can ignore that for now (and once its > ready they will propose patches, so we just have to do reviews). > > 1) Review all outstanding nova/python-novaclient sync patches. > https://review.openstack.org/#/c/72596/ > https://review.openstack.org/#/c/74560/ > https://review.openstack.org/#/c/75644/ > 2) Using update.sh sync all low hanging fruit in both repos all at > once. Low hanging fruit is anything that doesn't require a change > outside of */openstack/common. As usual when doing these syncs we > should list all patches being synced across, as well as document which > modules we aren't syncing accross > ./update.sh --base novaclient --config-file > ../python-novaclient/openstack-common.conf --dest-dir > ../python-novaclient/ > https://review.openstack.org/#/c/76642/ > ./update.sh --base nova --config-file ../nova/openstack-common.conf > --dest-dir ../nova/ > 3) At this point we should have a list of modules that are non-trivial > to sync, now we can triage them and decide if they are oslo bugs or if > nova/python-novaclient code needs updating. > > > So for now we need reviews on the patches listed in 1, and someone to > work on the low hanging fruit sync for nova. Followed by triaging of > the non-low hanging fruit. > > Once we have the low hanging fruit out of the way lets sync up about > how to handle the rest. > > best, > Joe > > > On Fri, Feb 21, 2014 at 6:26 PM, ChangBo Guo <glongw...@gmail.com> wrote: >> >> >> >> 2014-02-22 5:09 GMT+08:00 Ben Nemec <openst...@nemebean.com>: >> >>> /me finally catches up on -dev list traffic... >>> >>> On 2014-02-19 20:27, Doug Hellmann wrote: >>> >>> >>> >>> >>> On Wed, Feb 19, 2014 at 8:13 PM, Joe Gordon <joe.gord...@gmail.com> wrote: >>>> >>>> Hi All, >>>> >>>> As many of you know most oslo-incubator code is wildly out of sync. >>>> Assuming we consider it a good idea to sync up oslo-incubator code >>>> before cutting Icehouse, then we have a problem. >>>> >>>> Today oslo-incubator code is synced in ad-hoc manor, resulting in >>>> duplicated efforts and wildly out of date code. Part of the challenges >>>> today are backwards incompatible changes and new oslo bugs. I expect >>>> that once we get a single project to have an up to date oslo-incubator >>>> copy it will make syncing a second project significantly easier. So >>>> because I (hopefully) have some karma built up in nova, I would like >>>> to volunteer nova to be the guinea pig. >>> >>> >>> Thank you for volunteering to spear-head this, Joe. >>> >>> +1 >>>> >>>> To fix this I would like to propose starting an oslo-incubator/nova >>>> sync team. They would be responsible for getting nova's oslo code up >>>> to date. I expect this work to involve: >>>> * Reviewing lots of oslo sync patches >>>> * Tracking the current sync patches >>>> * Syncing over the low hanging fruit, modules that work without changing >>>> nova. >>>> * Reporting bugs to oslo team >>>> * Working with oslo team to figure out how to deal with backwards >>>> incompatible changes >>>> * Update nova code or make oslo module backwards compatible >>>> * Track all this >>>> * Create a roadmap for other projects to follow (re: documentation) >>>> >>>> I am looking for volunteers to help with this effort, any takers? >>> >>> >>> I will help, especially with reviews and tracking. >>> >>> I'm happy to help as well. I always try to help with oslo syncs any time >>> I'm made aware of problems anyway. >>> >>> What is our first step here? Get the low-hanging fruit syncs proposed all >>> at once? Do them individually (taking into consideration the module deps, >>> of course)? If we're going to try to get this done for Icehouse then we >>> probably need to start ASAP. >>> >>> -Ben >> >> I also would like to be volunteer of the new team :) >> -gcb >> >> >> -- >> ChangBo Guo(gcb) >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev