Thanks for starting the discussion around on this Alex! Much appreciated
and needed.
I agree with all the points here :) I'm a big proponent of predictable time
based releases.
As an aside, should we spin up a working group for releases? Given the
frequency of our releases and burn down meetings
Folks,
for more than a year Apache Mesos releases are done according to our "then
new" release policy [1]. It seems to work quite well, but today I would
like to address things that can be improved.
Let's start with pain points:
* A minor bug can cancel a release vote, even for a patch release.
2 matches
Mail list logo
