You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Daniel Shahaf <d....@daniel.shahaf.name> on 2011/08/23 12:21:52 UTC

1.7.0-rc1 on svn.apache.org

Do we recommend infra to install 1.7.0-rc1 on svn.apache.org?

---

Per [1], svn.us would have to be upgraded before svn.eu.

With my infra hat, I remind everyone that infra may decide not to
upgrade for a variety of reasons.  (For example, whether svn.eu and
svn.us are generally healthy or undergo concurrent changes at the time.)

[1] 
    http://mid.gmane.org/20110805030630.GA8206@daniel3.local
    Date: Fri, 5 Aug 2011 06:06:30 +0300
    From: Daniel Shahaf <da...@apache.org>
    To: dev@subversion.apache.org
    Subject: Re: 1.7 write-through proxy to 1.6 master
    Message-ID: <20...@daniel3.local>

Re: 1.7.0-rc1 on svn.apache.org

Posted by Julian Foad <ju...@wandisco.com>.
Daniel Shahaf wrote:
> Do we recommend infra to install 1.7.0-rc1 on svn.apache.org?

+1.

- Julian


> ---
> 
> Per [1], svn.us would have to be upgraded before svn.eu.
> 
> With my infra hat, I remind everyone that infra may decide not to
> upgrade for a variety of reasons.  (For example, whether svn.eu and
> svn.us are generally healthy or undergo concurrent changes at the time.)
> 
> [1] 
>     http://mid.gmane.org/20110805030630.GA8206@daniel3.local
>     Date: Fri, 5 Aug 2011 06:06:30 +0300
>     From: Daniel Shahaf <da...@apache.org>
>     To: dev@subversion.apache.org
>     Subject: Re: 1.7 write-through proxy to 1.6 master
>     Message-ID: <20...@daniel3.local>



Re: 1.7.0-rc1 on svn.apache.org

Posted by Greg Stein <gs...@gmail.com>.
Yes.
On Aug 23, 2011 6:22 AM, "Daniel Shahaf" <d....@daniel.shahaf.name> wrote:
> Do we recommend infra to install 1.7.0-rc1 on svn.apache.org?
>
> ---
>
> Per [1], svn.us would have to be upgraded before svn.eu.
>
> With my infra hat, I remind everyone that infra may decide not to
> upgrade for a variety of reasons. (For example, whether svn.eu and
> svn.us are generally healthy or undergo concurrent changes at the time.)
>
> [1]
> http://mid.gmane.org/20110805030630.GA8206@daniel3.local
> Date: Fri, 5 Aug 2011 06:06:30 +0300
> From: Daniel Shahaf <da...@apache.org>
> To: dev@subversion.apache.org
> Subject: Re: 1.7 write-through proxy to 1.6 master
> Message-ID: <20...@daniel3.local>

Re: 1.7.0-rc1 on svn.apache.org

Posted by Joe Schaefer <jo...@yahoo.com>.
When infra does move svn to the 1.7 candidates,

we're committed to only moving forward with that,
not back to a previous 1.6.  So as long as we're
all confident that serious problems can be addressed
in a reasonable period of time, I'm +1 as well.




>________________________________
>From: Hyrum K Wright <hy...@wandisco.com>
>To: C. Michael Pilato <cm...@collab.net>
>Cc: Daniel Shahaf <d....@daniel.shahaf.name>; dev@subversion.apache.org
>Sent: Tuesday, August 23, 2011 8:52 AM
>Subject: Re: 1.7.0-rc1 on svn.apache.org
>
>On Tue, Aug 23, 2011 at 7:06 AM, C. Michael Pilato <cm...@collab.net> wrote:
>> On 08/23/2011 06:29 AM, Daniel Shahaf wrote:
>>> - Bert points out that the HTTPv2 code may not interact well with
>>>   clients committing via the svn.eu mirror to an HTTPv2-enabled svn.us.
>>
>> Hrm, I can't think of any scenarios in which having a newer master version
>> than slave version will cause issues.  (It's the reverse case that can be
>> problematic.)  But then, I'm not completely awake yet, either.
>
>Although I don't want to be playing fast-and-loose with the ASF repo,
>running the RC on svn.apache.org would give us just the type of
>testing in these types of scenarios that's difficult to do manually.
>
>Assuming there is a decent "what to do if this thing borks the server"
>plan, I'm +1.
>
>-Hyrum
>
>
>-- 
>
>uberSVN: Apache Subversion Made Easy
>http://www.uberSVN.com/
>
>
>

Re: 1.7.0-rc1 on svn.apache.org

Posted by Hyrum K Wright <hy...@wandisco.com>.
On Tue, Aug 23, 2011 at 8:49 AM, Daniel Shahaf <d....@daniel.shahaf.name> wrote:
> Hyrum K Wright wrote on Tue, Aug 23, 2011 at 07:52:06 -0500:
>> On Tue, Aug 23, 2011 at 7:06 AM, C. Michael Pilato <cm...@collab.net> wrote:
>> > On 08/23/2011 06:29 AM, Daniel Shahaf wrote:
>> >> - Bert points out that the HTTPv2 code may not interact well with
>> >>   clients committing via the svn.eu mirror to an HTTPv2-enabled svn.us.
>> >
>> > Hrm, I can't think of any scenarios in which having a newer master version
>> > than slave version will cause issues.  (It's the reverse case that can be
>> > problematic.)  But then, I'm not completely awake yet, either.
>>
>> Although I don't want to be playing fast-and-loose with the ASF repo,
>> running the RC on svn.apache.org would give us just the type of
>> testing in these types of scenarios that's difficult to do manually.
>>
>> Assuming there is a decent "what to do if this thing borks the server"
>> plan, I'm +1.
>>
>
> We'll backup the pre-upgrade data and binaries.
>
> If the post-upgrade data gets corrupted, we'll be depending on the
> corruption not propagating to the mirrors on the 1.6 slave. (and we'll
> have to downtime the us mirror whilst the backups are promoted)
>
> If the upgrade compromises the machine... it's going to be fun.

Heh.  Glad to see you've thought about it.

I'd also like to take the opprotunity to remind folks that rc1 isn't
official yet (and there's currently some speculation in IRC that it
might never be), so you may want to hold off upgrading until an
official release is made.

-Hyrum

-- 

uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com/

Re: 1.7.0-rc1 on svn.apache.org

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Hyrum K Wright wrote on Tue, Aug 23, 2011 at 07:52:06 -0500:
> On Tue, Aug 23, 2011 at 7:06 AM, C. Michael Pilato <cm...@collab.net> wrote:
> > On 08/23/2011 06:29 AM, Daniel Shahaf wrote:
> >> - Bert points out that the HTTPv2 code may not interact well with
> >>   clients committing via the svn.eu mirror to an HTTPv2-enabled svn.us.
> >
> > Hrm, I can't think of any scenarios in which having a newer master version
> > than slave version will cause issues.  (It's the reverse case that can be
> > problematic.)  But then, I'm not completely awake yet, either.
> 
> Although I don't want to be playing fast-and-loose with the ASF repo,
> running the RC on svn.apache.org would give us just the type of
> testing in these types of scenarios that's difficult to do manually.
> 
> Assuming there is a decent "what to do if this thing borks the server"
> plan, I'm +1.
> 

We'll backup the pre-upgrade data and binaries.

If the post-upgrade data gets corrupted, we'll be depending on the
corruption not propagating to the mirrors on the 1.6 slave. (and we'll
have to downtime the us mirror whilst the backups are promoted)

If the upgrade compromises the machine... it's going to be fun.

> -Hyrum
> 
> 
> -- 
> 
> uberSVN: Apache Subversion Made Easy
> http://www.uberSVN.com/

Re: 1.7.0-rc1 on svn.apache.org

Posted by Hyrum K Wright <hy...@wandisco.com>.
On Tue, Aug 23, 2011 at 7:06 AM, C. Michael Pilato <cm...@collab.net> wrote:
> On 08/23/2011 06:29 AM, Daniel Shahaf wrote:
>> - Bert points out that the HTTPv2 code may not interact well with
>>   clients committing via the svn.eu mirror to an HTTPv2-enabled svn.us.
>
> Hrm, I can't think of any scenarios in which having a newer master version
> than slave version will cause issues.  (It's the reverse case that can be
> problematic.)  But then, I'm not completely awake yet, either.

Although I don't want to be playing fast-and-loose with the ASF repo,
running the RC on svn.apache.org would give us just the type of
testing in these types of scenarios that's difficult to do manually.

Assuming there is a decent "what to do if this thing borks the server"
plan, I'm +1.

-Hyrum


-- 

uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com/

Re: 1.7.0-rc1 on svn.apache.org

Posted by "C. Michael Pilato" <cm...@collab.net>.
On 08/23/2011 06:29 AM, Daniel Shahaf wrote:
> - Bert points out that the HTTPv2 code may not interact well with
>   clients committing via the svn.eu mirror to an HTTPv2-enabled svn.us.

Hrm, I can't think of any scenarios in which having a newer master version
than slave version will cause issues.  (It's the reverse case that can be
problematic.)  But then, I'm not completely awake yet, either.

-- 
C. Michael Pilato <cm...@collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Re: 1.7.0-rc1 on svn.apache.org

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Daniel Shahaf wrote on Tue, Aug 23, 2011 at 13:21:52 +0300:
> Do we recommend infra to install 1.7.0-rc1 on svn.apache.org?
> 
> ---
> 
> Per [1], svn.us would have to be upgraded before svn.eu.

Will there be an issue with having 1.6 on svn.eu and 1.7 on svn.us?

+ It would mean the svn.eu copies of the repositories can serve as
  a backup in case the svn.us copies get corrupted by some bug.

- Bert points out that the HTTPv2 code may not interact well with
  clients committing via the svn.eu mirror to an HTTPv2-enabled svn.us.

Done. Re: 1.7.0-rc1 on svn.apache.org

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
https://svn-master.apache.org/ now runs 1.7.0-rc1.

(This is also https://svn.apache.org/ for those of you whose DNS
resolvers are closer to USA than to Europe.)