For me upgrading to 7.8 was very easy. The release slippage actually helped out with that. 7.8 had already been specified well enough and already had some active users for a long time. This made for a long window for package maintainers to update their packages to have 7.8 compatibility. Perhaps October is a good timeline to try to cut an initial alpha release that specifies the interface for package authors to compile against, but the actual release can wait until later.


On Fri, May 30, 2014 at 2:46 PM, Simon Marlow <marlowsd@gmail.com> wrote:
On 27/05/14 09:06, Austin Seipp wrote:
PPS: This might also impact the 7.10 schedule, but last Simon and I
talked, we thought perhaps shooting for ICFP this time (and actually
hitting it) was a good plan. So I'd estimate on that a 7.8.4 might
happen a few months from now, after summer.

FWIW, I think doing 7.10 in October is way too soon.  Major releases create a large distributed effort for package maintainers and users, and there are other knock-on effects, so we shouldn't do them too often.  A lot of our users want stability, while many of them also want progress, and 12 months between major releases is the compromise we settled on.

The last major release slipped for various reasons, but I don't believe that means we should try to get back on track by having a short time between 7.8 and 7.10.  7.8 will be out of maintenance when it has only just made it into a platform release.

Anyway, that's my opinion.  Of course if everyone says they don't mind a 7.10 in October then I withdraw my objection :-)

(as a data point, upgrading to 7.8 at work cost me three weeks, but we're probably a special case)

Cheers,
Simon


_______________________________________________
Glasgow-haskell-users mailing list
Glasgow-haskell-users@haskell.org
http://www.haskell.org/mailman/listinfo/glasgow-haskell-users