[cinder] propose to EOL cinderlib train and ussuri
At last week's cinder project midcycle [0], the team discussed recent fixes to keep the cinderlib CI functional in the oldest stable branches. At this point, stable/train is running the bare minimum of CI to keep the branch open, and stable/ussuri is running only one functional job in excess of the bare minimum. The only changes merged into either branch since each was tagged -em have been non-functional, so we believe that there is no demand for keeping the branches open. Thus, the following patches to EOL cinderlib train and ussuri have been posted: - https://review.opendev.org/c/openstack/releases/+/853534 - https://review.opendev.org/c/openstack/releases/+/853535 This email serves as notice of the intent of the cinder project to EOL the cinderlib train and ussuri branches. If you have comments or concerns, please reply to this email or leave a comment on the appropriate patch. [0] https://etherpad.opendev.org/p/cinder-zed-midcycles
It's been two weeks and the silence has been deafening, so I'd like to ask the release team to merge the EOL patches at their earliest convenience, and then delete the train and ussuri cinderlib branches. cheers, brian On 8/17/22 3:38 PM, Brian Rosmaita wrote:
At last week's cinder project midcycle [0], the team discussed recent fixes to keep the cinderlib CI functional in the oldest stable branches. At this point, stable/train is running the bare minimum of CI to keep the branch open, and stable/ussuri is running only one functional job in excess of the bare minimum. The only changes merged into either branch since each was tagged -em have been non-functional, so we believe that there is no demand for keeping the branches open.
Thus, the following patches to EOL cinderlib train and ussuri have been posted: - https://review.opendev.org/c/openstack/releases/+/853534 - https://review.opendev.org/c/openstack/releases/+/853535
This email serves as notice of the intent of the cinder project to EOL the cinderlib train and ussuri branches. If you have comments or concerns, please reply to this email or leave a comment on the appropriate patch.
participants (1)
-
Brian Rosmaita