J Aaron Farr wrote:
A couple of days ago I asked about what needed to be done to help Fortress and
some other packages get a release out.  Quite a few things were mentioned, such
as Javadocs, general documentation, tests, etc.  I'm wondering how I should go
about submitting all this.  In particular, I'm working on some Javadocs and I'd
like to get some general notes down about building my first project with
Fortress.  The info I've seen on the main jakarta site seems to be targeted
towards committers more than contributers.  Should I email updates to a
particular individual?  Is there some article or guideline that I've missed
which discusses this?
probably, but I'm sure it's not easy to find :D

- patches which are bugfixes should go into bugzilla.
- other patches should be build as unified diffs (-u option); include [patch] in the subject line. Send them to the dev list.
- you can also add documentation to the wiki, http://nagoya.apache.org/wiki/apachewiki.cgi?AvalonProjectPages, but please no patches or stuff like that in the wiki.
- for other documentation, we maintain them as 'xdocs', ie xml files, we're moving stuff over to use the forrest (http://xml.apache.org/forrest/) dtds

if you have lots of new materials, it's also okay to provide a zip or tgz file somewhere along with instructions, instead of patches; whatever works.

Perhaps this should be on the dev list, but I'm sure other users have this
question from time to time.
yep. Another way of contributing: updating http://nagoya.apache.org/wiki/apachewiki.cgi?AvalonFAQ to answer that kind of question :D

Thanks,
hey, thank you!

cheers,

- Leo



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

Reply via email to