[erlang-questions] minor releases in Erlang?

Michael Truog mjtruog@REDACTED
Thu Dec 4 09:14:27 CET 2014

Even just a simple announcement that a new tag exists could help it receive testing.  That could make these minor updates more of a real "open source" release, due to public communication that encourages its use publicly.  The extra testing would help us determine when an Erlang release will not fail in testing or production due to bugs.

On 12/03/2014 01:14 PM, Benoit Chesneau wrote:
> It has been probably answered before, but what is the reason to not make official release for minor updates? Ie. when a version is tagged a release could be made available to the community. Today that could be done using any CI tool so I guess the reason is other.
> I am asking because today an SSL issue was raised in hackney.  I am generally using the latest tag, or recent version so I didn't noticed that the code I was using wasn't working for all certificates on previous version:
> https://github.com/benoitc/hackney/issues/141
> I am not sure right now how to solve such issue. Is there a way to test the minor version available?  On the other hand sometimes as a temporary workaround I could point someone to use the last release. But in this case that not simple, since it imply a build and in some infrastructure it would be impossible. How others do?
> - benoit
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20141204/50b7c32c/attachment.htm>

More information about the erlang-questions mailing list