Reply in-line.

On 23/08/18 00:32, Doug Hellmann wrote:
Monasca team,

It looks like you have self-proposed some, but not all, of the
patches to import the zuul settings into monasca repositories.

I found these:

+-----------------------------------------------------+--------------------------------+--------------+------------+-------------------------------------+---------------+
| Subject                                             | Repo                    
       | Tests     | Workflow   | URL                                 | Branch  
      |
+-----------------------------------------------------+--------------------------------+--------------+------------+-------------------------------------+---------------+
| Removed dependency on supervisor                    | openstack/monasca-agent 
       | VERIFIED | MERGED     | https://review.openstack.org/554304 | master   
     |
| fix tox python3 overrides                           | openstack/monasca-agent 
       | VERIFIED | MERGED     | https://review.openstack.org/574693 | master   
     |
| fix tox python3 overrides                           | openstack/monasca-api   
       | VERIFIED | MERGED     | https://review.openstack.org/572970 | master   
     |
| import zuul job settings from project-config        | openstack/monasca-api   
       | VERIFIED | MERGED     | https://review.openstack.org/590698 | 
stable/ocata  |
| import zuul job settings from project-config        | openstack/monasca-api   
       | VERIFIED | MERGED     | https://review.openstack.org/590355 | 
stable/pike   |
| import zuul job settings from project-config        | openstack/monasca-api   
       | VERIFIED | MERGED     | https://review.openstack.org/589928 | 
stable/queens |
| fix tox python3 overrides                           | 
openstack/monasca-common       | VERIFIED | MERGED     | 
https://review.openstack.org/572910 | master        |
| ignore python2-specific code under python3 for pep8 | 
openstack/monasca-common       | VERIFIED | MERGED     | 
https://review.openstack.org/573002 | master        |
| fix tox python3 overrides                           | 
openstack/monasca-log-api      | VERIFIED | MERGED     | 
https://review.openstack.org/572971 | master        |
| replace use of 'unicode' builtin                    | 
openstack/monasca-log-api      | VERIFIED | MERGED     | 
https://review.openstack.org/573015 | master        |
| fix tox python3 overrides                           | 
openstack/monasca-statsd       | VERIFIED | MERGED     | 
https://review.openstack.org/572911 | master        |
| fix tox python3 overrides                           | 
openstack/python-monascaclient | VERIFIED | MERGED     | 
https://review.openstack.org/573344 | master        |
| replace unicode with six.text_type                  | 
openstack/python-monascaclient | VERIFIED | MERGED     | 
https://review.openstack.org/575212 | master        |
|                                                     |                         
       |           |            |                                     |         
      |
|                                                     |                         
       | VERIFIED: 13 | MERGED: 13 |                                     |      
         |
+-----------------------------------------------------+--------------------------------+--------------+------------+-------------------------------------+———————+

They do not include the monasca-events-api, monasca-specs,
monasca-persister, monasca-tempest-plugin, monasca-thresh, monasca-ui,
monasca-ceilometer, monasaca-transform, monasca-analytics,
monasca-grafana-datasource, and monasca-kibana-plugin repositories.

It also looks like they don’t include some necessary changes for
some branches in some of the other repos, although I haven’t checked
if those branches actually exist so maybe they’re fine.

We also need a patch to project-config to remove the settings for
all of the monasca team’s repositories.

I can generate the missing patches, but doing that now is likely
to introduce some bad patches into the repositories that have had
some work done, so you’ll need to review everything carefully.

In all, it looks like we’re missing around 80+ patches, although
some of the ones I have generated locally may be bogus because of
the existing changes.

I realize Witold is OOO for a while, so I'm emailing the list to
ask the team how you want to proceed. Should I go ahead and propose
the patches I have?
Thanks Doug, we had a discussion and we agreed that the best way to proceed is for you to submit your patches and we will carefully review them.

Doug

__________________________________________________________________________
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


__________________________________________________________________________
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