Hi all,

I'm realizing that it happens from time to time that I let some
patches sleep for a long time in the git repo of a maintenance branch.

In fact the reason is simple : if we fix something really important, I
still have it in mind and can rush a release (except recently where I
forgot about this). But if we fix non-critical things, fixes can
accumulate for quite some time before either we get a big bug or
someone asks for a release.

So my question is : what do you think about the current maintenance
release frequency ? Do you think we should release more often, which
also means that some people might upgrade for no good reason, or get
used to miss versions ? Do you think that instead we should simply
consider that when someone asks for a release here on the list, it's
likely the good time for it ?

I tend to think we could try this second option, with all of us being
more vocal about the releases. When someone would like to see a release
emitted, maybe simply ask for it on the list. This tends to cause a lot
of "me too" responses which are a good indicator that a release is worth
being pushed. And probably that after that we'd find the "optimal" frequency.

That's just an idea of course. I'd rather avoid mechanisms such as "release
after 2 weeks without bugs" since it's the best way to forget about the
release (in fact that's more or less what I'm trying to do, and it does
not work that well). And in parallel, sometimes I'd rather delay a release
a little bit because a known bug is being investigated.

Ideas and suggestions are welcome.

Thanks,
Willy


Reply via email to