[2253] in athena10
Re: [Debathena] #172: Make a website with information about
daemon@ATHENA.MIT.EDU (Debathena Trac)
Mon Apr 13 16:29:54 2009
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
From: "Debathena Trac" <debathena@MIT.EDU>
Cc: debathena@mit.edu
To: broder@mit.edu, wdc@mit.edu
Date: Mon, 13 Apr 2009 20:28:36 -0000
Reply-To:
Message-ID: <052.6c899cd6503949a73b9047f141ccabff@mit.edu>
In-Reply-To: <043.92db855d8a04fd80c11c072db21dfd05@mit.edu>
Content-Transfer-Encoding: 8bit
#172: Make a website with information about -proposed-------------------+--------------------------------------------------------
Reporter: broder | Owner:
Type: defect | Status: new
Priority: major | Component: website
Keywords: |
-------------------+--------------------------------------------------------
Comment(by wdc):
I've looked at the "proposed" and "development" pages as they currently
exist.
I have a couple questions:
1. How are these pages kept up to date? I hope there's a script that runs
so they're actually always in sync with reality.
2. Is there a page that points at these two pages? I couldn't find links
to them.
Some time ago, I suggested we needed documentation that explained what
these two releases were. In email I sent on 15 March to a few folks I
said:
I think it's very important that we be able to provide simple
description
akin to jdreed's:
alpha = development, beta=proposed, and early machines get put in
either
public or beta, depending on what their owners want.
Broder's email of 6 March to debathena subject header: "Apt repository
layout" contains a LOT of good description. I'd really like to see some of
that on the web site, and perhaps such a page would then link to the
proposed and development package list sub-pages.
-- Ticket URL: <http://debathena.mit.edu/trac/ticket/172#comment:2>Debathena <http://debathena.mit.edu/>MIT Debian-Athena Project
