pereinar    2002/07/02 00:58:54

  Modified:    .        ANNOUNCE
  Log:
  Corrected some stuff in announce and added correct links.
  
  Revision  Changes    Path
  1.3       +23 -12    modperl-docs/ANNOUNCE
  
  Index: ANNOUNCE
  ===================================================================
  RCS file: /home/cvs/modperl-docs/ANNOUNCE,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ANNOUNCE  2 Jul 2002 05:28:56 -0000       1.2
  +++ ANNOUNCE  2 Jul 2002 07:58:54 -0000       1.3
  @@ -1,18 +1,18 @@
   What?
   -----
   
  -As you may know, the work on the new mod_perl site have started in
  +As you may know, the work on the new mod_perl site started in
   September 2001, and after almost a year we are glad to present to you
   the outcome of this work. The new site's goal wasn't only to create a
   nice design, but mainly to improve its documentation organization and
  -navigation aspects, because of the ever growing amount of
  +navigational aspects, because of the ever growing amount of
   documentation that the mod_perl community generates.
   
   We have now come to the point where we are very satisfied with the
   design and overall usability of the site, so we are proud to announce
   the Release Candidate 1. Depending on the feedback from you, the site
  -may undergo some minor fixes if there are problems and eventually be
  -released for you all to use.
  +may undergo some minor fixes if there are problems and will eventually
  +be released for you all to use.
   
   Where?
   ------
  @@ -21,8 +21,8 @@
   
        http://perl.apache.org/release/
   
  -When the Release Candidate gets all bugs rolled out, it will replace
  -the existing mod_perl site:
  +When the Release Candidate gets all its bugs rolled out, it will
  +replace the existing mod_perl site:
   
        http://perl.apache.org/
   
  @@ -48,11 +48,11 @@
   these standards didn't exist at the time of their release) or simply
   broken. However, we still tried to make the site usable for these
   browsers, which also somewhat restricted us in deploying the standards
  -to their full extent. 
  +to their full extent.
   
  -So if you see a rendering problem, in an old, buggy or alpha version
  -of some browser, but the site is still usable you may have to live
  -with that and possibly you will need to consider upgrading your
  +So if you see a rendering problem in a browser that is known not to
  +support these standards, but the site is still usable, you may have to
  +live with that and possibly you will need to consider upgrading your
   browser.
   
   The text browsers "lynx" and "links" seem to work fine with the new
  @@ -64,7 +64,8 @@
   one. We will *not* try to provide a solution for every browser out
   there, because we simply don't have the resources for that, and we
   don't want to maintain a dozen css style sheets to accomodate for
  -idiosyncrasies of every browser.
  +idiosyncrasies of every browser. However, we do want to get it to work
  +as best as possible for everyone.
   
   Also we would like to remind you that you've had many chances to
   influence the overall design of the site and at this point it's too
  @@ -78,9 +79,15 @@
   
   Before reporting a problem, first please check whether the problem
   that you've have been reported already here:
  -    http://perl.apache.org/site-issues.txt
  +
  +    http://perl.apache.org/ISSUES
  +
   If your issue is already listed, please do not submit it again.
   
  +For a list of working OS/browser combinations, see here:
  +
  +    http://perl.apache.org/STATUS
  +
   Otherwise please post the description of the problem to the docs-dev
   list:
   
  @@ -100,6 +107,10 @@
   - a detailed report of the *exact* problem you are having
   - if you have a rendering problem please provide a snapshot, though
     please try to keep the snapshot's size small.
  +
  +If the site is working OK for you, and it's not listed at
  +http://perl.apache.org/STATUS , you can send us an "OK" report so that
  +we know what works and what doesn't.
   
   Please be as precise as possible to help us find out the problem and
   fix it. Furthermore, if you know hot to fix the problem, we will
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to