[sage-devel] Re: Trac downtime for upgrades

[Dima Pasechnik]

On 2018-05-11, Jeroen Demeyer  wrote:
> I wouldn't worry about it too much especially if you expect the downtime 
> to be relatively short. Just do the upgrade...

indeed
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Trac downtime for upgrades

[Dima Pasechnik]

On 2018-05-11, Jeroen Demeyer  wrote:
> I wouldn't worry about it too much especially if you expect the downtime 
> to be relatively short. Just do the upgrade...

indeed.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Trac downtime for upgrades

[Erik Bray]

On Fri, May 11, 2018 at 6:08 PM, Erik Bray  wrote:
> On Fri, May 11, 2018 at 5:12 PM, Erik Bray  wrote:
>> On Fri, May 11, 2018 at 11:47 AM, Erik Bray  wrote:
>>> Hi all,
>>>
>>> I have some long overdue updates for Sage's Trac that I've been
>>> putting off deploying for several months, for various reasons.
>>> However, I believe it *is* ready to deploy.
>>>
>>> This upgrade will require a database migration, so it will require
>>> taking the site down for a few minutes to perform a backup and do the
>>> migration.
>>>
>>> I would prefer not to do it on a weekend, so I was wondering if there
>>> is a good time today to do it..  I would propose 17:00 GMT+2, as I
>>> suspect not too many people will be working around that time (even in
>>> the US).  Is that alright for everyone?  I believe the downtime should
>>> be about 20 minutes.
>>
>> Upgrade completed--only took about 5 minutes actually :)
>>
>> The main difference you should notice, if anything, is that the links
>> to branches on tickets no longer directly contain an
>> https://git.sagemath.org URL.  Now they go through
>> trac.sagemath.org/git-merger
>> This is part of a performance enhancement that delays creating merge
>> previews until the merge preview is actually visited.
>>
>> Everything else should work more or less the same, but if anything
>> seems amiss let me know in this thread.
>
> It seems the "(Commit)" links next to branches in tickets are now
> broken.  I don't recall having a problem like this in testing.  I'll
> look into it.

Okay, I pushed a patch release that should fix that issue.  Don't know
why I didn't catch that before (other than the fact that the plugin
doesn't have a test suite :)

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Trac downtime for upgrades

[Erik Bray]

On Fri, May 11, 2018 at 5:12 PM, Erik Bray  wrote:
> On Fri, May 11, 2018 at 11:47 AM, Erik Bray  wrote:
>> Hi all,
>>
>> I have some long overdue updates for Sage's Trac that I've been
>> putting off deploying for several months, for various reasons.
>> However, I believe it *is* ready to deploy.
>>
>> This upgrade will require a database migration, so it will require
>> taking the site down for a few minutes to perform a backup and do the
>> migration.
>>
>> I would prefer not to do it on a weekend, so I was wondering if there
>> is a good time today to do it..  I would propose 17:00 GMT+2, as I
>> suspect not too many people will be working around that time (even in
>> the US).  Is that alright for everyone?  I believe the downtime should
>> be about 20 minutes.
>
> Upgrade completed--only took about 5 minutes actually :)
>
> The main difference you should notice, if anything, is that the links
> to branches on tickets no longer directly contain an
> https://git.sagemath.org URL.  Now they go through
> trac.sagemath.org/git-merger
> This is part of a performance enhancement that delays creating merge
> previews until the merge preview is actually visited.
>
> Everything else should work more or less the same, but if anything
> seems amiss let me know in this thread.

It seems the "(Commit)" links next to branches in tickets are now
broken.  I don't recall having a problem like this in testing.  I'll
look into it.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Trac downtime for upgrades

[Erik Bray]

On Fri, May 11, 2018 at 11:47 AM, Erik Bray  wrote:
> Hi all,
>
> I have some long overdue updates for Sage's Trac that I've been
> putting off deploying for several months, for various reasons.
> However, I believe it *is* ready to deploy.
>
> This upgrade will require a database migration, so it will require
> taking the site down for a few minutes to perform a backup and do the
> migration.
>
> I would prefer not to do it on a weekend, so I was wondering if there
> is a good time today to do it..  I would propose 17:00 GMT+2, as I
> suspect not too many people will be working around that time (even in
> the US).  Is that alright for everyone?  I believe the downtime should
> be about 20 minutes.

Upgrade completed--only took about 5 minutes actually :)

The main difference you should notice, if anything, is that the links
to branches on tickets no longer directly contain an
https://git.sagemath.org URL.  Now they go through
trac.sagemath.org/git-merger
This is part of a performance enhancement that delays creating merge
previews until the merge preview is actually visited.

Everything else should work more or less the same, but if anything
seems amiss let me know in this thread.

Thanks,
E

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.