Re: link to devel/release_info
Since Richard will probably be the release manager, he has been added
to the reply. There is a summary at the end so you know where this is
On Thu, Mar 18, 1999 at 09:09:02AM -0800, Darren Benham wrote:
> On Thu, Mar 18, 1999 at 01:25:50AM -0500, James A. Treacy wrote:
> > Although I understand the reasoning behind removing the link, as
> > the person who answers most of the mail sent to webmaster, I'm
> > not happy it. Perhaps the information mentioned above can be added
> > to the release notes under releases/stable.
> What was the reasoning?
For most people, the information under releases/slink is sufficient.
It is common, though, for people looking into switching Linux
distributions to ask, "what kernel and version of X does Debian use?"
(I just use those as examples. I'm sure others will want to add to
the list). I don't think Adam was aware that there was a reason for
the link so I'm not upset with him and hope no one else is either.
Additionally, it looks like he has offered to add that information to
the release notes.
> > I'd like to see something that is managed by the release manager.
> > They should have a grasp on both where Debian is and where it
> > is going. The release notes included with each release can then be
> > generated from the information on this page.
> Will the release manager do it, though? That's the important question. We
> can't dictate to him/them (when the post gets filled, has Richard been
> confirmed in the post?)
I agree. Unless we ask these questions, there is no way we will find the
This whole issue is release related. As it stands, what goes into
a release is decided rather haphazardly (at least it appears that way).
Even when a decision is made only those close to the decision are
generally aware of it. We need a release manager/group that makes
decisions AND keeps a web page up to date for all the world to see.
P.S. Richard, this discussion arose when a link was removed from the main
debian web page pointing to devel/release_info.html. This document has
a history of not being well maintained - in large part because it is
difficult to get information. A release manager/group that is doing its
job should have an easy time maintaining this page, in large part because
they make the final decision on what goes into a release.