From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10210091836.AA19630@clio.rice.edu>
Subject: Re: DJGPP Clio 2.04 WIP update
To: djgpp-workers AT delorie DOT com
Date: Wed, 9 Oct 2002 13:36:32 -0500 (CDT)
In-Reply-To: <200210091629.g99GT1l24848@envy.delorie.com> from "DJ Delorie" at Oct 09, 2002 12:29:01 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> > I propose a new page, probably on DJ's server, which gives a history
> > of a release, refreshes, and pointers to known fixes or workarounds
> > for bugs.
> 
> What, besides the "what changed" section of the online knowledge base?
> 
> http://www.delorie.com/djgpp/doc/kb/kb_2.html
 (this isn't current with 2.03 refresh, by the way ...)

I'm thinking of a higher level, something like:
  January 2000 2.03 Release (size, date)
  March   2000  refresh (size, date) added DSM
  Dec     2001  refresh (size, date) fixes (link to kb ...)
  June    2002  refresh (size, date) header fixes

Link to known problems/workarounds/patches not fixed in most recent refresh
  (Today for 2.03 this would be stat() on devices w2k patch, and some
   workaround notes for Win2K/XP).  A place to collect patches between
   refreshes.  Could just be a directory browse.  Similar to the list
   of fixes Eli kept and built with when he did binary distributions.
   A happy medium between the standard package and CVS of the day.

Goal would be a quick summary so you could tell if a distribution on a
CD (or on your hard disk) was the most recent one, or what you are 
missing.  Is this for the base (djdev/djcrx) only, or key distributions?

Maybe this would be a place to remember why we keep some distributions
around.  (You can't get GCC 2.x from the zip picker.  We know why we are
keeping it, but it ought to be on a web page why we are keeping it).

> But a top-level link to a summary page would be OK with me too.  More
> incentive to get more of the djgpp web pages into cvs.

I think this stuff belongs under the KB structure you already have,
I'm just not exactly sure where yet.