Opened 8 years ago

Closed 6 years ago

#2353 enhancement closed fixed (fixed)

Change Twisted "main" release to a time-based version number

Reported by: glyph Owned by:
Priority: normal Milestone: twisted-8.0
Component: release management Keywords:
Cc: itamarst Branch:
Author: Launchpad Bug:

Description

Probably similar to Ubuntu's.

Change History (11)

comment:1 Changed 8 years ago by glyph

This is, of course, dependent on time-based releases, which is dependent on #2308.

comment:2 Changed 8 years ago by glyph

Other notes from the meeting:

  • The new release number is going to be 7.x, where x is the month that we do the release in.
  • Twisted Core's version number is NOT changing to this scheme, so that we don't have the confusion where Core is synchronized with Twisted but nothing else is.

comment:3 Changed 8 years ago by thomasvs

What does this mean ? Is this the version number of the Sumo tarball ?
Isn't this going to be even more confusing ?

Also, have you thought of what you will do in 2100 ? In 3000 ?

comment:4 Changed 8 years ago by exarkun

The idea is that having the Twisted version (what you called the "Sumo tarball") be different from the Twisted Core version (as it is already different from every other Twisted subproject version) will be less confusing than having them be the same.

comment:5 Changed 8 years ago by itamarst

  • Cc itamarst added

This should be 2007.x, not 7.x. It's confusing to users to have 7.x, since it looks like version number, so there's assumption about majorness when digit changes, etc..

Ubuntu's numbering scheme initially confused me, so I had to read a FAQ. The fact there's a FAQ is not a good sign, we should learn from their mistakes.

You can still draw a logo with a 7 even if the official version is 2007.x. ;)

comment:6 Changed 8 years ago by glyph

I still like having the number be "7". Shorter numbers have more of an impact and are easier to remember, especially considering that there will be numbers after that first dot.

I'll concede, however, that this is not a terribly important issue compared to the other release management issues we're working on, so if we're going to disagree, let's put off talking about it until we've managed to get a few shorter-cycle releases out which haven't broken all kinds of compatibility :).

comment:7 Changed 7 years ago by jml

  • Milestone set to twisted-7.0

comment:8 Changed 7 years ago by therve

For the record, there are several references to Twisted 2.6 (and even Twisted 2.7), especially in deprecation warnings. We must be careful to jump these numbers for release.

comment:9 Changed 6 years ago by radix

I've fixed the references to 2.6 and 2.7 in the branch for the 8.0 release (#3085)

comment:10 Changed 6 years ago by radix

  • Resolution set to fixed
  • Status changed from new to closed

Version scheme has been changed and Twisted 8 is out.

comment:11 Changed 3 years ago by <automation>

  • Owner radix deleted
Note: See TracTickets for help on using tickets.