[erlang-questions] Fwd: FW: Fwd: Fwd: SSL peer verification in httpc with Mozilla's certificate store

[Tuncer Ayaz]

On Sun, Sep 14, 2014 at 5:17 PM, Andreas Schumacher wrote:
> External maintainers can ignore the versions that are not officially
> announced as a major release or service package, and for which
> neither source/binary packages nor documentation are published on
> erlang.org. Nevertheless, in order to increase transparency and to
> avoid similar confusion and discussions in the future, we could
> announce those patch packages on erlang-questions. Then external
> maintainers can decide themselves whether they want to include those
> packages into their products.

I don't mind tag-only releases, and actually _appreciate_ it very much,
so thanks a lot! The confusion is, from what I can tell, based on the
fact that 17.1 was announced but 17.2 was not.

If commit messages and git history is maintained in a descriptive and
consistent state, you could automate release notes with links to the
relevant commits. But right now there are somtimes intermediate and
other commits you'd have to filter from auto-generated release notes.
For example, try 'git shortlog OTP-17.1.2...OTP-17.2.2', and you'll
find 'wip' commits that ideally would have been amended or squashed.

That said, does the OTP team backport fixes to old releases? If they
do, such tags (without an official release) can be useful for various
production nodes.