db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject Re: Derby web site updates [Ken, please 'svn update' to make visible]
Date Thu, 02 Sep 2004 20:13:59 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Rodent of Unusual Size wrote:

| Daniel John Debrunner wrote:
|
|>Can someone explain the web-site process? A Derby committer can make
|>changes to the source pages for the web-site but does not have the
|>permissions to make them visible on the actual site. Hence the requests
|>to Ken to 'svn update to make visible'. Is Ken in a committer++ role or
|>~ as a committer on the incubator project or something else?
|
|
| more or less, yes.  there are four different kinds of access involved:
|
| a) access to the derby site module (svn incubator/derby/site/trunk/)
| b) access to the incubator module (cvs incubator/)
| c) access to the incubator site module (cvs incubator-site/)
| d) access to the web server filesystems
|
| there are two places on the incubator site where the derby project has
| pages:
|
| 1. http://incubator.apache.org/derby/
| 2. http://incubator.apache.org/projects/derby.html
|
| #1 comes from the derby site module, and is quite straightforward:
| any time someone with [a] access changes the derby site module, someone
| with [d] access needs to propagate those changes to the web server.

Thanks for the clear explanation, one more question though.

Does the #1 process ever become automated, e.g. once out of incubation,
or is there always a manual step asking someone with d) to perform the
magic?

Dan.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFBN38GIv0S4qsbfuQRAkLvAKDbmMNdyE1gcMi6Yd06EE+Vu3MMuQCfTZ1p
4bX67VpTpppnfsePu+ZUpYA=
=4Yf5
-----END PGP SIGNATURE-----


Mime
View raw message