Simon Michael
2018-11-15 15:25:02 UTC
I have been doing major releases on the last day of the quarter for two years. Now I'm thinking of relaxing the strict schedule a little, to:
- get useful features and fixes into the hands of users more quickly and more often. I assume a significant number of users will install releases from hackage/stackage but not unreleased code from github.
- keep more in step with the haskell ecosystem. Expanding on https://github.com/simonmichael/hledger/issues/883: <https://github.com/simonmichael/hledger/issues/883:> GHC is now released every six months; GHC 8.6 arrived just before hledger 1.11. Adding support for that is a big enough change that it should be a major hledger release, but that is not scheduled till 12/31. That would mean three months without a released version of hledger that can support the increasingly popular latest GHC version. That might be ok, but it also means we are excluded from Stackage nightly for a long time, harder to install with stack, and at risk of missing a new stackage LTS release.
- reduce release work. Counter intuitively I think having a more frequent release window will avoid some work that I might otherwise have to do.
Proposed new policy:
- ship major releases when needed/wanted
- but normally at most one major release per month, at least one per quarter
- normal release window is "soon after the start of each month". Eg it could be the 1st, or the 4th, or later (I am usually busy in the first week of october).
- get useful features and fixes into the hands of users more quickly and more often. I assume a significant number of users will install releases from hackage/stackage but not unreleased code from github.
- keep more in step with the haskell ecosystem. Expanding on https://github.com/simonmichael/hledger/issues/883: <https://github.com/simonmichael/hledger/issues/883:> GHC is now released every six months; GHC 8.6 arrived just before hledger 1.11. Adding support for that is a big enough change that it should be a major hledger release, but that is not scheduled till 12/31. That would mean three months without a released version of hledger that can support the increasingly popular latest GHC version. That might be ok, but it also means we are excluded from Stackage nightly for a long time, harder to install with stack, and at risk of missing a new stackage LTS release.
- reduce release work. Counter intuitively I think having a more frequent release window will avoid some work that I might otherwise have to do.
Proposed new policy:
- ship major releases when needed/wanted
- but normally at most one major release per month, at least one per quarter
- normal release window is "soon after the start of each month". Eg it could be the 1st, or the 4th, or later (I am usually busy in the first week of october).
--
You received this message because you are subscribed to the Google Groups "hledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hledger+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "hledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hledger+***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.