On Mon, Apr 08, 2019 at 11:52:49AM +0000, Jens Harbott wrote:
The Chef OpenStack project still has a set of repos with stable/newton branches, however those have been announced as EOL for more than a year [0], but we missed to actually close them down. I plan to do so in a couple of days unless there is some justified objection. See [1] for a list of the affected repositories and the commit hashes that are targeted to receive the "newton-eol" tag.
That all looks okay to me. I'm not certain how to fix up the review in openstack/releases but I *think* as we're EOL'ing the branch we should just omit that from the change.
The situation with the stable/ocata branches is similar, but while we did announce them as EOL in [0], too, the date mentioned there seems wrong.
Yeah that date is a little wrong you went EOL 4 days after release :P
Also, there seems to be some confusion about the situation for the global OpenStack project, which doesn't seem to have retired stable/ocata for any project yet.
Ocata went into Extended Maintenance a while back but we're just now working out that we didn't complete the full process. Once Sean's work in [1] is merged we should have a consistent view of the state for Ocata.[0]
Still, we don't have any open patches for stable/ocata, we don't have a working CI for it, and there also isn't anyone using it known to me. So please respond if there is a reason to keep the stable/ocata branches in their current state, otherwise I'd start the process to tag them as EOL, too.
I think you're okay to EOL them but I suspect that it'd be good to wait until the dust settles on the Stein release, and the Ocata/Pike transition to EM. Which more or less means the week after summit. Would that work for you? Yours Tony. [0] Which seems to NOT include openstack-chef ? [1] https://review.openstack.org/#/q/status:open+project:openstack/releases+bran...