[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#294827: marked as done (please add an "Upgrading" page and link it from the main page)

Your message dated Fri, 19 Aug 2011 15:52:47 -0500
with message-id <20110819205247.GA13322@elie.gateway.2wire.net>
and subject line Re: please add an "Upgrading" page and link it from the main page
has caused the Debian Bug report #294827,
regarding please add an "Upgrading" page and link it from the main page
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
294827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=294827
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: www.debian.org
Severity: wishlist
Tags: patch

Searching through google and looking at the front page, it is not
trivial to find out how to upgrade from one release to the next (sic!).

One has to be wittful enough to guess that "Release Info" could be the
link to use, but this seems far from evident (at least for me).

If Debian wants people to be able to upgrade easily and to attract
people to test the "woody->sarge" upgrade process, then it needs to
make finding the relevant, important information.
*t

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.22
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

--- End Message ---
--- Begin Message --- 
Hi,

Tomas Pospisek wrote:

> Searching through google and looking at the front page, it is not
> trivial to find out how to upgrade from one release to the next (sic!).

The front page says

	* If you're upgrading to the latest stable release from a
	  previous version, please read [the release notes] before
	  proceeding.

I think that means this is fixed at last.  Thanks for reporting it.

--- End Message ---
Reply to: