In #294857 I suggested to put something like the following into the
release notes ***but only until sarge is released*** (thus removing it on
the release date):
Untill sarge is released (and possibly after that too) please add the
following as a first paragraph to the chapter "Reporting Bugs":
---------------------------------------------------------------------
If you are testing the upgrade procedure on a testing release and
you encounter problems that can not or are difficult to attributed to
specific packages then please issue a bugreport on the "upgrade-reports"
pseudo package.
---------------------------------------------------------------------
Since sarge has been out now for a while, I suggest to put the same into
the etch release notes ***but only until etch is released***.
The rationale for my suggestion is that *if* someone *does* go through the
effort of beta testing upgrades/installation, then s/he will most probably
read the release notes for guidance (among others because problems can be
expected with an alpha/beta release).
So it was my thinking that that would be the place to put such a statement
to channel the flow of feedback to where it belongs - namely to the
upgrade-reports pseudo package.
(/me is wondering, why any of the follow-up discussion reached him)
The important point is *not* that this information absolutely needs to be
displayed 'somewhere'. The point is that it needs to be on the critical
path of the documents that the potential tester *will* read.
So Don's suggestion:
On Wed, 15 Nov 2006, Don Armstrong wrote:
The current instructions already appear to handle this case
appropriately:
You should check if your bug report has already been filed by
someone else before submitting it. Lists of currently
outstanding bugs are available on the World Wide Web and
elsewhere ÿÿ see other documents for details. You can submit
your comments to an existing bug report #<number> by sending
e-mail to <number>@bugs.debian.org
If you can't seem to determine which package contains the
problem, please send e-mail to the [Debian user mailing list]
asking for advice. If your problem doesn't relate just to one
package but some general Debian service, there are several
[pseudo-packages] or even [mailing lists] that you can use to
relay your message to us instead.
If the current pseudopackage description isn't accurate, changing that
may be in order.
doesn't make much sense in the context of the original intent, since:
upgrade-reports - Reports of upgrade problems for stable & testing
'only' shows up on a subpage of a subpage of a subpage of bugs.debian.org
and thus is arguably far, far away from the "critical path" and thus
unlikely to be stumbled over by a tester.
Difficulty to find the appropriate place to report upgrade bugs at the
time (Feb.2005) was probably the reason for this suggestion.
I think Frans suggestion:
I agree that it definitely does not belong in the RN.
Maybe it could be mentioned on the webpage for the testing release
(which needs to be modified anyway when it becomes stable).
is reasonable. A link from http://www.debian.org/releases/testing/ to
http://bugs.debian.org/upgrade-reports could be of help to upgrade/install
testers.
If someone could say based on fact, whether the little reports on that
page are due to the quality of the coming release/installer or due to the
testers not knowing the 'upgrade-reports' pseudo package, then we'd have
an objective base for the decision on where and if to include the
suggested blurb.
Please, if you disagree, then close this bug.
Thanks and greets,
*t
--
--------------------------------------------------------
Tomas Pospisek
http://sourcepole.com - Linux & Open Source Solutions
--------------------------------------------------------
