Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (nike.apache.org: domain of nbeyer@gmail.com designates
 209.85.210.177 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=lqM1kuw+kDik00UiSuyA6F/AiFdRZdCGNN93PizoKhqvQFPVMSQ10NsIg9IR4VpYMS
         B2htqu4I3S6JVHBNZlt6rxyJnkx2AJ38MePUYIlOCSkB1pF4ekChIDTVF+jGlHWXm2U8
         l899dgJgjzmf4OitH/7gLW+ehT6XNltN6vXAw=
MIME-Version: 1.0
Sender: nbeyer@gmail.com
In-Reply-To: <200909031828.n83ISnhA012822@d06av04.portsmouth.uk.ibm.com>
References: <200909031828.n83ISnhA012822@d06av04.portsmouth.uk.ibm.com>
Date: Thu, 3 Sep 2009 20:51:47 -0500
Message-ID: <3b3f27c60909031851h56867773w30457b502eb69c93@mail.gmail.com>
Subject: Re: [website] Testing SVN based websites (fwd)
From: Nathan Beyer <ndbeyer@apache.org>
To: dev@harmony.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

+1 and +1

On Thu, Sep 3, 2009 at 1:28 PM, Mark Hindess<mark.hindess@googlemail.com> w=
rote:
>
> The infra team are testing a new svn-based publishing system for project
> websites - see below for some details. =C2=A0I think this technology is m=
uch
> nicer because it is faster so there is less waiting around to see if
> your update worked (and less waiting around for the fix to be propagated
> if it didn't). =C2=A0I also like the idea of using branches to make use o=
f
> harmony.staging.apache.org so you can *really* test your changes before
> copying the trunk to the live branch.
>
> What do other people think about:
>
> 1) using a branch to distinguish the live site from trunk. =C2=A0I think =
the
> overhead of an extra svn copy to promote staging to live is well worth
> the additional peace of mind when making changes.
>
> 2) volunteering harmony.apache.org to be a test site. =C2=A0We don't make
> many changes so it should be fairly low risk.
>
> Regards,
> =C2=A0Mark.
>
> ------- Forwarded Message
>
> Date: Thu, 3 Sep 2009 03:18:51 -0700
> Message-ID: <4239a4320909030318s4fe3b877md4b094a6bbbb49a7@mail.gmail.com>
> Subject: Testing SVN based websites
> From: Paul Querna <paul@querna.org>
> To: infrastructure-dev@apache.org
>
> Hi,
>
> SvnWcSub and SvnPubSub now work well enough for some testing.
>
> I have added a staging.apache.org subdomain for now.
>
> I have setup a required user/pass for all *.staging.apache.org, NOT to
> make it secure, but to prevent googlebot etc from indexing it.
>
> First demo:
> http://apr.staging.apache.org/
> Username: staging
> Password: staging
>
> Commits <https://svn.apache.org/repos/asf/apr/site/trunk/docs> to are
> propagated the live webserver in under 1 second.
>
> The use of a staging path is entirely up to the PMC/TLP, the sync
> tools only care about subversion paths -- for example, we could map
> them like this:
> apr.apache.org -> https://svn.apache.org/repos/asf/apr/site/branches/live=
/docs
> apr.staging.apache.org -> https://svn.apache.org/repos/asf/apr/site/trunk=
/docs
>
> If a PMC thought that was a better workflow for them -- if a PMC
> prefers to just have instant updates, they can forgo the staging
> domain, and just map it to their live domain.
>
> So.... any Volunteer PMCs who want to convert their production website?
>
> SvnWcSub and SvnPubSub will still need some more development and a few
> small features, but so far seem very stable... yay for twisted and
> python.
>
> Thanks,
>
> Paul
>
> ------- End of Forwarded Message
>
>
>
>
>