Cloud Haskell Release Process & Branching Policy

[Tim Watson]

Hi all,

I'd like to get some input and confirmation on what the release and branching processes look for for Cloud Haskell. I'm not proposing to change anything (unless we think changes would be helpful), but rather would like to align the process for the downstream libraries I work on, and understand how it works for the base CH libraries.

Cheers,

Tim 

[Boespflug, Mathieu]

Hi Tim,

I think simple is crucial to avoid discouraging contributions. With
that motto in mind:

* master always represents the latest "trunk".
* master is considered pretty stable: we have a pretty thorough review
process for most patches.
* Cut new minor releases either on a regular basis (at least once a
month if there have been contributions), or on-demand to satisfy
downstream library authors, whichever comes first.
* If a PR contains a breaking change, don't wait to merge it to
master. Push a release branch to which future minor changes are
backported.
* For major releases, follow roughly the tempo of LTS Haskell (once
every 3 to 6 months), since users typically won't notice a new major
release until a new LTS major version bump anyways, and conversely
letting a major release drag means it won't be in LTS until a long
time afterwards. But only as a guideline.
* Backport bug fixes to older versions as long as new supported LTS
Haskell releases are cut by the Stackage team, at the maintainer's
discretion.

No merges from downstream branches, no rebases.

That's basically the process we've been following so far, though we've
been lucky enough to seldom (or never?) need release branches so far.

I hope this covers what you had in mind re "release and branching processes"?

Best,

--
Mathieu Boespflug
Founder at http://tweag.io.

> --
> You received this message because you are subscribed to the Google Groups
> "cloud-haskell-developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to cloud-haskell-deve...@googlegroups.com.
> To post to this group, send email to
> cloud-haskel...@googlegroups.com.
> Visit this group at
> https://groups.google.com/group/cloud-haskell-developers.
> For more options, visit https://groups.google.com/d/optout.

[Tim Watson]

Very much so. I'm going to adopt the same approach. Thanks for clarifying how it works Matthieu!

Cheers,
Tim