Saturday, 2022-05-07

gmannrosmaita: ack01:51
gmannit means we should finalize the new release cadence name ASAP before projects start more documentation on it01:52
gmannI still think SLURP is best choice here, as no name satisfy all the criteria/members 01:54
gmannspotz_: arne_wiebalck ^^ i know you both objected on this but if that is not so strong objection then should we go with this? or any idea you have?01:55
gmannbut we should conclude it very first thing in next week.01:57
*** prometheanfire is now known as Guest006:30
arne_wiebalckgmann: The suggestion is to tag/mark/name the OpenStack releases between which upgrades are possible while skipping releases in between as a "OpenStack SLURP" releases? Blame my (most likely non-existing :-) German humor, but for me that sounds a little as if we do not take the naming of these releases very seriously ... I would prefer sth more neutral such as "OpenStack SLU" release (in analogy with "Ubuntu LTS" 13:58
arne_wiebalckreleases), for instance. Maybe I just have to get used to the name ... so if all of you agree that SLURP will not give the above impression, disregard my objection :)13:58
*** Guest0 is now known as prometheanfire15:46
spotzgmann arne_wiebalckUeah I like SLU better then SLURP17:14
fungiwe can always appeas both, by having skip-level upgrade (SLU) releases, which follow the skip-level upgrade release process (SLURP). the former is used in designating the releases, while the latter is a term for the process documentation18:27
fungier, appease18:27
fungithough i also think we do need to remember to keep a bit of "fun" in openstack. if it's all serious all the time, that loses a bit of the project's friendly and enjoyable character18:29

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!