[dev][qa][devstack] Release management for QA toold and plugins

Thierry Carrez thierry at openstack.org
Wed Dec 5 10:32:51 UTC 2018


Ghanshyam Mann wrote:
>  ---- On Fri, 30 Nov 2018 19:05:36 +0900 Thierry Carrez <thierry at openstack.org> wrote ---- 
>  >  [...]
>  > OK so in summary: 
>  >  
>  > eslint-config-openstack, karma-subunit-reporter, devstack-tools ->  
>  > should be considered cycle-independent (with older releases history  
>  > imported). Any future release would be done through openstack/releases 
>  >  
>  > devstack-vagrant -> does not need releases or release management, will  
>  > be marked release-management:none in governance 
>  >  
>  > devstack-plugin-ceph -> does not need releases or cycle-related  
>  > branching, so will be marked release-management:none in governance 
>  >  
>  > Other devstack-plugins maintainers should pick whether they need to be  
>  > branched every cycle or not. Oslo-maintained plugins like  
>  > devstack-plugin-zmq and devstack-plugin-pika will, for example. 
>  >  
>  > Unless someone objects, I'll push the related changes where needed. 
>  > Thanks for the clarification ! 
> 
> +1. Those looks good. Thanks.

See:
https://review.openstack.org/622903
https://review.openstack.org/622904
https://review.openstack.org/#/c/622919/

Cheers,

-- 
Thierry Carrez (ttx)



More information about the openstack-discuss mailing list