Even though you probably all know, just for clarity our policy has been that
every release is a patch release until it isn’t. That is, as soon as something
other than a bug fix is added it becomes a minor release. Personally, I think
this still makes sense as it avoids needing the extra branch.
>From a user perspective, sometimes having releases too often leads to
upgrade fatigue. Eventually it becomes easier to not upgrade, because
so many things have changed in the interim that it becomes very
annoying to attempt to upgrade things. For comparison, Ubuntu will do
releases every 6
Hi Piotr,
I think scheduled releases that everybody can follow are great and your
proposal makes sense.
Does this also mean we don't have that many "noise" emails from upgraded
dependency (releases)?
I have come to realize in the past months that "inclusion" is most important,
and that would
Hi all,
Since we have a fast and easy release process now and a release does
not require a free weekend any more, I think we should have a regular
release schedule.
Unless something exceptional happens (e.g. big bug that renders
`log4j-jcl` unusable ;-) ), I would propose to:
* have a patch
