Ticket #1342 (closed feature request: fixed)

Opened 6 years ago

Last modified 5 years ago

Name major releases as "6.8.0" rather than "6.8"

Reported by: Isaac Dupree Owned by:
Priority: normal Milestone:
Component: Compiler Version: 6.7
Keywords: Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: Difficulty: Unknown
Test Case: Blocked By:
Blocking: Related Tickets:

Description

(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)

Change History

Changed 6 years ago by igloo

  • status changed from new to closed
  • resolution set to fixed

Another important point is that currently we get 6.6.YYYYMMDD snapshots for 6.6.1, which sort later than 6.6.1.

I've updated the version numbering policy, and in doing so found that the simplest way to avoid poor number sorting is to start at 6.8.1, with snapshots of the branch starting as 6.8.0.YYYYMMDD.

And as an added bonus we don't get any x.0 releases, which as we all know are buggier than x.1, x.2 etc!

Changed 6 years ago by Isaac Dupree

Even better :-)

Changed 5 years ago by simonmar

  • architecture changed from Unknown to Unknown/Multiple

Changed 5 years ago by simonmar

  • os changed from Unknown to Unknown/Multiple
Note: See TracTickets for help on using tickets.