[prev in list] [next in list] [prev in thread] [next in thread]
List: apache-bugdb
Subject: documentation/8893: Dating HTTPD Release Announcements.
From: <uid0 () catastrophe ! net>
Date: 2001-11-28 22:45:18
[Download RAW message or body]
> Number: 8893
> Category: documentation
> Synopsis: Dating HTTPD Release Announcements.
> Confidential: no
> Severity: non-critical
> Priority: medium
> Responsible: apache
> State: open
> Quarter:
> Keywords:
> Date-Required:
> Class: doc-bug
> Submitter-Id: apache
> Arrival-Date: Wed Nov 28 14:50:00 PST 2001
> Closed-Date:
> Last-Modified:
> Originator: uid0@catastrophe.net
> Release: 1.3.22
> Organization:
apache
> Environment:
Any operating system.
> Description:
It may be wise to date your HTTPD announcements. Many people do not have the time to \
keep up-to-date on the Apache web site, and it is often difficult to remember what \
release we are running. By stating that Apache 1.3.22, released MM/DD/YYYY, it may \
help jar our horrible memory into recalling that we are down-level.
> How-To-Repeat:
Go to the Apache HTTPD Server announcement page.
> Fix:
See Full Description.
> Release-Note:
> Audit-Trail:
> Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or ]
["Re: general/1098:"). If the subject doesn't match this ]
[pattern, your message will be misfiled and ignored. The ]
["apbugs" address is not added to the Cc line of messages from ]
[the database automatically because of the potential for mail ]
[loops. If you do not include this Cc, your reply may be ig- ]
[nored unless you are responding to an explicit request from a ]
[developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic