openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "robert burrell donkin" <robertburrelldon...@gmail.com>
Subject Re: staging of site changes
Date Tue, 25 Jul 2006 21:06:28 GMT
On 7/25/06, Patrick Linskey <plinskey@bea.com> wrote:
> Hey,
>
> Does apache have any infrastructure / conventions in place for staging
> changes to the site to look them over / collaborate / etc. before
> pushing them to the site?

web pages are staged at people.apache.org before being rsync'd to
www.apache.org. it is possible to review changes before this happens -
see http://www.apache.org/dev/project-site.html.

however, this doesn't sound what you're looking for

in terms of general review, the standard procedures are review then
commit (RTC) and commit then review (CTR). when CTR is being used, all
committers should read and review the commit email. when RTC is being
used, committers use JIRA to post their proposed changes and then wait
till the vote passed.

but this probably isn't what you wanted to know either :-)

a common way of gathering feedback, the usual approach is to use your
personal webspace (http://people.apache.org/~rdonkin in my case) to
host the documentation on a temporary basis. this approach has
limitations when it comes to collaboration. unless the source is
committed, there are limits to the quantity of collaboration that's
possible. it's good for people posting a few corrections and
improvement but deep collaboration between a group of documentors
probably requires a branch.

http://www.apache.org/dev/new-committers-guide.html#public_html covers
the personal web space for committers.

- robert

Mime
View raw message