Hi Thierry and all, Os-acc is not relevant and will be discontinued. This was communicated in [1]. A patch has been filed for the same [2].
I will start the work after Train-3 milestone. That was also mentioned in [3].
[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008473.ht... [2] https://review.opendev.org/#/c/676331/ [3] https://review.opendev.org/#/c/680091/
Regards, Sundar
-----Original Message----- From: Sean Mooney smooney@redhat.com Sent: Monday, September 9, 2019 7:42 AM To: Thierry Carrez thierry@openstack.org; openstack- discuss@lists.openstack.org Subject: Re: [release][cyborg] os-acc status
On Mon, 2019-09-09 at 16:27 +0200, Thierry Carrez wrote:
Hi Cyborgs,
One of your deliverables is the os-acc library. It has seen no change over this development cycle and therefore was not released at all in train.
We have several options for this library now:
1- It's still very much alive and desired and just has exceptionally not seen much activity during this cycle. We should just cut a stable/train branch from the last release available (0.2.0) and continue in
ussuri.
2- It's a valuable library, it just changes extremely rarely. We should make it independent from the release cycle and have it release at its own rhythm.
3- Development has stopped on this, and the library is not useful right now. We should retire this deliverable so that we do not build wrong expectations for our users.
i think ^ is the case. i dont activly work on cyborg but i belive os-acc is no longer planned to be used or developed. they can correct me if that is wrong but i think it can be removed as a deliverable.
Please let us know which option fits the current status of os-acc.