Ubuntu

Documentation uses codenames, no match with release numbers

Bug #268435 reported by ak
4
Affects Status Importance Assigned to Milestone
Ubuntu Documentation
Invalid
Undecided
Unassigned
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

The entire ubuntu support documentation except release notes uses release codenames (eg hardy, breezy), but there does not appear anywhere a mapping of codenames to release numbers. Further, use of codenames forces readers to go figure out the release number in order to determine where in the life cycle the document resides (eg is it too new for me or too old, or just right?).

The use of codenames interferes with access to the information.

Suggested solution: abadon use of codenames completely, except for unreleased projects. If a codename does appear anywhere, for example in discussion about a future project, provide a mapping to a definition of the codename.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report.

You can find information about releases at https://wiki.ubuntu.com/Releases . Is it what you're looking for ?

Revision history for this message
James Westby (james-w) wrote :

Hi,

Thanks for your report, I am reassigning it to the documentation project.

Thanks,

James

Revision history for this message
Matthew East (mdke) wrote :

Hi,

It's been Ubuntu's policy for a long time to use release numbers and not codenames (https://wiki.ubuntu.com/CodeNamesToVersionNumbers and https://help.ubuntu.com/community/WikiGuide/WritingGuide)

Can you point out instances where codenames are used and they should not be? If so, we can fix them.

Changed in ubuntu-doc:
status: New → Incomplete
Revision history for this message
ak (akujbida) wrote :

Hi,
    That table at https://wiki.ubuntu.com/CodeNamesToVersionNumbers is superb, I had been looking for a long time for it (now it's stuck to my cubicle wall). I don't have page names with this problem at hand, but when I come across them, what shall I do, append to this bug or raise a new one for each that I find?
Regards,
Aleksander

Revision history for this message
Old_Soldier (charles.davis) wrote :

If the page is on help.ubuntu.com/community you can always edit the page yourself to make the fix. If the page is immutable please raise a bug on that particular page rather than make this a "meta-bug".

Revision history for this message
Matthew East (mdke) wrote :

Ak - yes, you can open a bug for each example you find in the shipped documents, or for the wiki documents, either fix it directly as Old_Soldier suggests, or open a bug. I'll close this in the absence of any concrete examples.

Changed in ubuntu-doc:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.