[m-rev.] for review: configure --enable-ssdebug-grades

Paul Bone pbone at csse.unimelb.edu.au
Thu Jul 29 14:48:12 AEST 2010


On Thu, Jul 29, 2010 at 01:36:32PM +1000, Peter Wang wrote:
> On 2010-07-29, Paul Bone <pbone at csse.unimelb.edu.au> wrote:
> > On Thu, Jul 29, 2010 at 12:39:45PM +1000, Peter Wang wrote:
> > > Branches: main, 10.04
> > > 
> > 
> > I don't understand our policy regarding 10.04.  Since this patch doesn't fix a
> > bug I don't know why we would include it on a release branch.  Presumably _if_
> > we release a 10.04.1 it would only contain fixes to 10.04 and not new features.
> 
> Releases are for users (i.e. MC ;-)), and getting new features out to users,
> if they are definitely undisruptive, would seem to be good policy.
> This change in particular is especially user-centric.

Isn't that the point of a 6-monthy release?

Or maybe we should do a monthy 'preview' version that's less stable than the
releases.

Either way, I think that bugfixes should only go onto the 10.04 branch so that
it can be re-released if sagnificant bugs are fixed.

> > Any reson for not suggesting ./configure --enable-libgrades=<explicit list> ?
> 
> The person to whom the message is addressed presumably has no idea what
> a "grade" is.  I don't think you'll find it spelt out in any of the
> top-level documentation files either.

Isn't this just a better way of doing:
    make -j4 install LIBGRADES='hlc.gc asm_fast.gc.decldebug'

And this still doesn't say what a grade is.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 489 bytes
Desc: Digital signature
URL: <http://lists.mercurylang.org/archives/reviews/attachments/20100729/7f98fd8b/attachment.sig>


More information about the reviews mailing list