On Sat, Feb 09, 2013 at 12:06:12PM +, Simon Marlow wrote:
>
> As a straw man, let's suppose we want to do annual API releases in
> September, with intermediate non-API releases in February.
That's a non-API release 5 months after the API release.
6.10.2 was 5 months after 6.10.1 (.3 was 1
On Sat, Feb 9, 2013 at 6:27 AM, Simon Peyton-Jones wrote:
> In short, I think we already have the situation that you desire. Perhaps
> we just need to market it better?
>
> ** **
>
> Or am I mistaken?
>
Except the current question is about how ghc releases interact with the
Platform; this
I agree too - I think it would be great to have non-API-breaking
releases with new features. So let's think about how that could work.
Some features add APIs, e.g. SIMD adds new primops. So we have to
define non-API-breaking as a minor version bump in the PVP sense; that
is, you can add to a
If there's a path to having a release strategy as Manuel suggests, and having
an intermediate release with the new vector primops, type extensions and such
goodness, then I'm all for it. A lot of these bits are things ill start using
almost immediately in production / real software, esp if I'm
