id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,os,architecture,failure,difficulty,testcase,blockedby,blocking,related
1342,"Name major releases as ""6.8.0"" rather than ""6.8""",Isaac Dupree,,"(It seems that for specific requests Trac is better for getting responses and generally recording what happens than the mailing list. So I'm copying this here and will consider that in future.)

I've gotten confused before between whether GHC ""6.6"" referred to the
whole branch or the point release between 6.4.2 and 6.6.1.  It makes it
hard to distinguish which is being referred to (although, it also makes
it easy to be vague when referring to an upcoming major release, which
might be considered an advantage I suppose).  I propose we switch to
that ""X.Y.0""-style major release naming as of 6.8.0 (a.k.a. 6.8).

(GCC's having made this naming change inspired me to suggest this,
but I don't actually know what their reasons were)",feature request,closed,normal,,Compiler,6.7,fixed,,,Unknown/Multiple,Unknown/Multiple,,Unknown,,,,