Project

General

Profile

Actions
Copy link

Bug #4168

closed

Upgrading order for 2.8 is not sufficiently visible

Bug #4168: Upgrading order for 2.8 is not sufficiently visible

Added by Jonathan CLARKE over 12 years ago. Updated almost 11 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
Documentation
Target version:
2.8.1
Pull Request:
https://github.com/Normation/rudder-d...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Looking at http://www.rudder-project.org/rudder-doc-2.8/rudder-doc.html#_upgrade_rudder, the first thing you read is commands to run to upgrade Rudder. I will bet many $$$ that users will run these faster, and not ever scroll down to the overview that chapter "Caution cases" provides. This chapter needs to be moved to the top of that section.

Updated by Jonathan CLARKE over 12 years ago Actions
Copy link
 #1

  • Status changed from In progress to Pending technical review
  • Pull Request set to https://github.com/Normation/rudder-doc/pull/42

Updated by Jonathan CLARKE over 12 years ago Actions
Copy link
 #2

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset commit:1e4700148dfa64cf9fb2e51939e062b52a07ca08.

Updated by Jonathan CLARKE over 12 years ago Actions
Copy link
 #3

Applied in changeset commit:7eb8cb7aaff4f9d549d89ab42defd32e49e61458.

Updated by Nicolas PERRON over 12 years ago Actions
Copy link
 #4

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.8.1, which was released today.
Check out:

Updated by Benoît PECCATTE almost 11 years ago Actions
Copy link
 #5

  • Project changed from 30 to Rudder
  • Category set to Documentation
Actions
Copy link

Also available in: PDF Atom