Activity log for bug #419788

Date Who What changed Old value New value Message
2009-08-27 09:05:23 Matthew Paul Thomas bug added bug
2009-08-27 09:06:06 Matthew Paul Thomas description 1. Go to <https://launchpad.net/ubuntu/jaunty>, and look at the main heading and any global navigation. 2. Go to <https://launchpad.net/ubuntu/jaunty>, and look at the main heading and any global navigation. What you see: 1. Jaunty 2. Karmic What you should see (at least until October 29): 1. Ubuntu 9.04 2. Ubuntu Karmic The convention for distribution vendors is to refer to a distribution series by its codename before release, and by its version number after release. For example, <http://www.ubuntu.com/> prominently features "Ubuntu 9.04", and does not mention the word "Jaunty". <https://wiki.ubuntu.com/CodeNamesToVersionNumbers> explains that "The names of each release (e.g., Breezy Badger, Dapper Drake) are development code names and typically for internal use only ... We don't want to use the version numbers prior to the actual release, as it increases the likelihood that a pre-release version will be mistaken for a final release. Similarly, we don't want the code names to be visible to the user once the final release has been made." Similarly, <http://www.debian.org/> says "The latest stable release of Debian is 5.0", and does not mention the word "lenny". Conversely, <http://www.debian.org/releases/> gives a codename "squeeze" for the next version, but not a version number. Launchpad should reflect this convention, without series maintainers having to update a field manually on release day. Specifically: * The distribution series .displayname database field should be renamed to .codename. * A distribution series .displayname should be a cached property, equal to its .codename when the series has not yet been released, and to its .version after it has been released. * The main heading for a distribution series overview page should consist of the distribution.displayname plus the distroseries.displayname. This is part of <https://dev.launchpad.net/RegistrySimplifications>. 1. Go to <https://launchpad.net/ubuntu/jaunty>, and look at the main heading and any global navigation. 2. Go to <https://launchpad.net/ubuntu/karmic>, and look at the main heading and any global navigation. What you see: 1. Jaunty 2. Karmic What you should see (at least until October 29): 1. Ubuntu 9.04 2. Ubuntu Karmic The convention for distribution vendors is to refer to a distribution series by its codename before release, and by its version number after release. For example, <http://www.ubuntu.com/> prominently features "Ubuntu 9.04", and does not mention the word "Jaunty". <https://wiki.ubuntu.com/CodeNamesToVersionNumbers> explains that "The names of each release (e.g., Breezy Badger, Dapper Drake) are development code names and typically for internal use only ... We don't want to use the version numbers prior to the actual release, as it increases the likelihood that a pre-release version will be mistaken for a final release. Similarly, we don't want the code names to be visible to the user once the final release has been made." Similarly, <http://www.debian.org/> says "The latest stable release of Debian is 5.0", and does not mention the word "lenny". Conversely, <http://www.debian.org/releases/> gives a codename "squeeze" for the next version, but not a version number. Launchpad should reflect this convention, without series maintainers having to update a field manually on release day. Specifically: * The distribution series .displayname database field should be renamed to .codename. * A distribution series .displayname should be a cached property, equal to its .codename when the series has not yet been released, and to its .version after it has been released. * The main heading for a distribution series overview page should consist of the distribution.displayname plus the distroseries.displayname. This is part of <https://dev.launchpad.net/RegistrySimplifications>.
2009-08-31 13:57:08 Curtis Hovey launchpad-registry: importance Undecided Low
2009-08-31 13:57:10 Curtis Hovey launchpad-registry: status New Triaged
2010-03-25 17:40:54 Matthew Paul Thomas description 1. Go to <https://launchpad.net/ubuntu/jaunty>, and look at the main heading and any global navigation. 2. Go to <https://launchpad.net/ubuntu/karmic>, and look at the main heading and any global navigation. What you see: 1. Jaunty 2. Karmic What you should see (at least until October 29): 1. Ubuntu 9.04 2. Ubuntu Karmic The convention for distribution vendors is to refer to a distribution series by its codename before release, and by its version number after release. For example, <http://www.ubuntu.com/> prominently features "Ubuntu 9.04", and does not mention the word "Jaunty". <https://wiki.ubuntu.com/CodeNamesToVersionNumbers> explains that "The names of each release (e.g., Breezy Badger, Dapper Drake) are development code names and typically for internal use only ... We don't want to use the version numbers prior to the actual release, as it increases the likelihood that a pre-release version will be mistaken for a final release. Similarly, we don't want the code names to be visible to the user once the final release has been made." Similarly, <http://www.debian.org/> says "The latest stable release of Debian is 5.0", and does not mention the word "lenny". Conversely, <http://www.debian.org/releases/> gives a codename "squeeze" for the next version, but not a version number. Launchpad should reflect this convention, without series maintainers having to update a field manually on release day. Specifically: * The distribution series .displayname database field should be renamed to .codename. * A distribution series .displayname should be a cached property, equal to its .codename when the series has not yet been released, and to its .version after it has been released. * The main heading for a distribution series overview page should consist of the distribution.displayname plus the distroseries.displayname. This is part of <https://dev.launchpad.net/RegistrySimplifications>. 1. Go to <https://launchpad.net/ubuntu/karmic>, and look at the main heading and any global navigation. 2. Go to <https://launchpad.net/ubuntu/lucid>, and look at the main heading and any global navigation. What you see: 1. "Karmic" 2. "Lucid" What you should see (at least until 2010-04-29): 1. "Ubuntu 9.10" 2. "Ubuntu Lucid" The convention for distribution vendors is to refer to a distribution series by its codename before release, and by its version number after release. For example, <http://www.ubuntu.com/> prominently features "Ubuntu 9.10", and does not mention the word "Karmic". <https://wiki.ubuntu.com/CodeNamesToVersionNumbers> explains that "The names of each release (e.g., Breezy Badger, Dapper Drake) are development code names and typically for internal use only ... We don't want to use the version numbers prior to the actual release, as it increases the likelihood that a pre-release version will be mistaken for a final release. Similarly, we don't want the code names to be visible to the user once the final release has been made." Similarly, <http://www.debian.org/> says "The latest stable release of Debian is 5.0", and does not mention the word "lenny". Conversely, <http://www.debian.org/releases/> gives a codename "squeeze" for the next version, but not a version number. Launchpad should reflect this convention, without series maintainers having to update a field manually on release day. Specifically: * The distribution series .displayname database field should be renamed to .codename. * A distribution series .displayname should be a cached property, equal to its .codename when the series has not yet been released, and to its .version after it has been released. * The main heading for a distribution series overview page should consist of the distribution.displayname plus the distroseries.displayname. This is part of <https://dev.launchpad.net/RegistrySimplifications>.
2010-03-25 17:56:22 Curtis Hovey launchpad-registry: milestone series-10.05
2010-03-25 17:56:27 Curtis Hovey launchpad-registry: importance Low High
2010-05-28 12:47:42 Matthew Paul Thomas description 1. Go to <https://launchpad.net/ubuntu/karmic>, and look at the main heading and any global navigation. 2. Go to <https://launchpad.net/ubuntu/lucid>, and look at the main heading and any global navigation. What you see: 1. "Karmic" 2. "Lucid" What you should see (at least until 2010-04-29): 1. "Ubuntu 9.10" 2. "Ubuntu Lucid" The convention for distribution vendors is to refer to a distribution series by its codename before release, and by its version number after release. For example, <http://www.ubuntu.com/> prominently features "Ubuntu 9.10", and does not mention the word "Karmic". <https://wiki.ubuntu.com/CodeNamesToVersionNumbers> explains that "The names of each release (e.g., Breezy Badger, Dapper Drake) are development code names and typically for internal use only ... We don't want to use the version numbers prior to the actual release, as it increases the likelihood that a pre-release version will be mistaken for a final release. Similarly, we don't want the code names to be visible to the user once the final release has been made." Similarly, <http://www.debian.org/> says "The latest stable release of Debian is 5.0", and does not mention the word "lenny". Conversely, <http://www.debian.org/releases/> gives a codename "squeeze" for the next version, but not a version number. Launchpad should reflect this convention, without series maintainers having to update a field manually on release day. Specifically: * The distribution series .displayname database field should be renamed to .codename. * A distribution series .displayname should be a cached property, equal to its .codename when the series has not yet been released, and to its .version after it has been released. * The main heading for a distribution series overview page should consist of the distribution.displayname plus the distroseries.displayname. This is part of <https://dev.launchpad.net/RegistrySimplifications>. 1. Go to <https://launchpad.net/ubuntu/lucid>, and look at the main heading and any global navigation. 2. Go to <https://launchpad.net/ubuntu/maverick>, and look at the main heading and any global navigation. What you see: 1. "Lucid" 2. "Maverick" What you should see: 1. "Ubuntu 10.04 LTS" 2. "Ubuntu Maverick" (until 2010-10-10) The convention for distribution vendors is to refer to a distribution series by its codename before release, and by its version number after release. For example, <http://www.ubuntu.com/> prominently features "Ubuntu 10.04 LTS", and does not mention the word "Lucid". <https://wiki.ubuntu.com/CodeNamesToVersionNumbers> explains that "The names of each release (e.g., Breezy Badger, Dapper Drake) are development code names and typically for internal use only ... We don't want to use the version numbers prior to the actual release, as it increases the likelihood that a pre-release version will be mistaken for a final release. Similarly, we don't want the code names to be visible to the user once the final release has been made." Similarly, <http://www.debian.org/> says "The latest stable release of Debian is 5.0", and does not mention the word "lenny". Conversely, <http://www.debian.org/releases/> gives a codename "squeeze" for the next version, but not a version number. Launchpad should reflect this convention, without series maintainers having to update a field manually on release day. Specifically: * The distribution series .displayname database field should be renamed to .codename. * A distribution series .displayname should be a cached property, equal to its .codename when the series has not yet been released, and to its .version after it has been released. * The main heading for a distribution series overview page should consist of the distribution.displayname plus the distroseries.displayname. This is part of <https://dev.launchpad.net/RegistrySimplifications>.
2010-12-03 05:16:33 Curtis Hovey tags distributions
2011-04-05 10:15:09 Gavin Panella tags distributions lp-registry derivation distributions lp-registry
2011-06-22 16:25:23 Julian Edwards launchpad: importance High Low