struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hus...@apache.org
Subject cvs commit: jakarta-struts/doc/faqs helping.xml
Date Mon, 05 Jul 2004 23:29:30 GMT
husted      2004/07/05 16:29:30

  Modified:    doc/faqs helping.xml
  Log:
  Routine updates.
  
  Revision  Changes    Path
  1.11      +23 -29    jakarta-struts/doc/faqs/helping.xml
  
  Index: helping.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-struts/doc/faqs/helping.xml,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -r1.10 -r1.11
  --- helping.xml	29 Feb 2004 22:55:45 -0000	1.10
  +++ helping.xml	5 Jul 2004 23:29:30 -0000	1.11
  @@ -77,8 +77,8 @@
   </p>
   
   <p>
  -If Struts doesn't do what <em>you</em> want, it's up to <strong>you</strong>
to step up
  -and propose the patch.
  +If Struts doesn't do what <em>you</em> want, it's up to <strong>you</strong>
to
  +step up and propose the patch.
   If Struts doesn't ship as often as you would like, it's up to you to step up
   with the tests and fixes that get a release out the door.
   </p>
  @@ -115,7 +115,7 @@
   
   <p>
   You can research and report outstanding fixes and feature requests using
  -<a href="http://jakarta.apache.org/site/bugs.html">Jakarta Bugzilla</a>.
  +<a href="http://jakarta.apache.org/site/bugs.html">Bugzilla</a>.
   If you are unsure if this is an actual problem, feel free to bring it up the
   list first.
   But to be sure that an issue is resolved, read
  @@ -131,7 +131,8 @@
   <p>
   <a href="http://jakarta.apache.org/site/source.html">Patches</a> are always
   welcome.
  -If you can't write a patch to fix your bug, a <a href="kickstart.html#tests">unit
test</a>
  +If you can't write a patch to fix your bug, a
  +<a href="kickstart.html#tests">unit test</a>
   that demonstrates the problem is also welcome.
   (And, of course, unit tests that prove your patch works are equally welcome.)
   </p>
  @@ -147,8 +148,8 @@
   to your local copy of Struts, and report whether it worked for you.
   Feedback from developers regarding a proposed patch is really quite
   helpful.
  -Don't hesitate to add a "works for me" note to a ticket if you've tried the patch yourself
  -and found it useful.
  +Don't hesitate to add a "works for me" note to a ticket if you've tried the
  +patch yourself and found it useful.
   </p>
   
   </section>
  @@ -162,7 +163,7 @@
   These are the same people who distribute the Apache Web server.
   Like all ASF projects, Struts is managed as a &quot;meritocracy&quot;,
   where everyone's contribution is welcome.
  -Users can help other users the
  +Users can help other users through the
   <a href="http://jakarta.apache.org/site/mail.html">mailing lists</a>,
   <a href="http://jakarta.apache.org/site/bugs.html">report bugs</a>, and
   <a href="http://jakarta.apache.org/site/bugs.html">request new features</a>.
  @@ -180,8 +181,8 @@
   </p>
   
   <p>
  -A very good place to start is by <strong>reviewing the list of open issues</strong>
and
  -pending feature requests (<a href="#bugs">Bugzilla</a>).
  +A very good place to start is by <strong>reviewing the list of open issues</strong>
  +and pending feature requests (<a href="#bugs">Bugzilla</a>).
   If you see an issue that needs a patch you can write,
   feel free to annex your patch.
   If you seen an issue that needs a unit test to prove its fixed,
  @@ -272,7 +273,8 @@
   </p>
   
   <p>
  -Jakarta products are released on the basis of merit, and ~not~ according
  +
  +Apache products are released on the basis of merit, and ~not~ according
   to a strict timetable.
   The volunteers devote whatever time they can to work on the product.
   But all volunteers have real jobs and real lives, that do take precedence.
  @@ -281,15 +283,7 @@
   </p>
   
   <p>
  -All Jakarta products must circulate a public beta before release.
  -If a beta is not in circulation,
  -then it's a good bet that a release is not forthcoming any time soon.
  -Products sometimes go through several betas before final release.
  -So if this is beta 1, then it still may not be released any time soon.
  -</p>
  -
  -<p>
  -The bottom line is that Jakarta takes releases very seriously.
  +The bottom line is that Apache takes releases very seriously.
   We do not compromise the quality of our software by watching the calendar
   (and then ship something ready or not).
   A release is ready when it is ready.
  @@ -310,7 +304,8 @@
   and whether what is being developed will meet your needs.
   If you need a feature right now, you can use the nightly build, or roll your
   own patch.
  -There are no private CVS's or private development lists.
  +There are no internal code repositories, private development lists,
  +secret chat rooms, or conference calls.
   What you see is what we got.
   If you are following the DEV list, then you know everything the developers
   know.
  @@ -338,8 +333,8 @@
   <ul>
   
   <li>
  -  Most importantly, <strong>download the latest beta</strong> or release-candidate
and
  -  test it against your own applications.
  +  Most importantly, download the lastest nightly build or development release
  +  and test it against your own applications.
     Report any and all issues or suspected issues to
     <a href="http://jakarta.apache.org/site/bugs.html">Bugzilla</a>.
     The sooner we resolve any problems, the fewer betas or release candidates
  @@ -384,9 +379,8 @@
     first.
     If an issue on your ballot doesn't include a patch, feel free to try coding
     one yourself.
  -  (At Jakarta, patches are the only votes that truly count.)
  -  Well over <a href="../volunteers.html">thirty developers</a> have contributed
  -  code or documentation to the product.
  +  (In a meritocracy, patches are the only votes that matter.)
  +  Dozens of developers have contributed code or documentation to Struts.
     You can too =:0)
   </li>
   
  @@ -405,8 +399,8 @@
       name="Who makes the final decisions regarding Struts">
   
   <p>
  -The management of the Jakarta site, and the Struts product, is based on
  -principles and practices used by creators of the Apache HTTPD server.
  +The management of the Struts product is based on principles and practices used
  +by creators of the Apache HTTPD server.
   Struts follows the
   <a href="http://jakarta.apache.org/site/guidelines.html">Project Guidelines</a>
   on the main Jakarta site.
  @@ -420,14 +414,14 @@
   </p>
   
   <p>
  -The Struts project has its own <a href="../using.html#Lists">Dev list</a>,
  +The Struts project has its own <a href="../using.html#Lists">DEV list</a>,
   where all of the decisions regarding Struts are made.
   Most development takes place via
   <a href="http://jakarta.apache.org/site/proposal.html#decisions/voting/items">
   Lazy Consensus</a>.
   Committers post most changes to the product unilaterally, using their own best
   judgment, and only discuss or vote upon controversial matters.
  -Another Committer can veto any change in an unreleased product with cause.
  +Struts PMC members can veto with cause any change in an unreleased product.
   </p>
   
   </section>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org


Mime
View raw message