I'd like to update syncStatic.sh to enforce the website change freeze (in case I accidentally run make push). Here is the patch for the change:
Index: syncStatic.sh =================================================================== RCS file: /cvs/puppet/configs/system/syncStatic.sh,v retrieving revision 1.20 diff -u -r1.20 syncStatic.sh --- syncStatic.sh 12 Dec 2007 23:11:07 -0000 1.20 +++ syncStatic.sh 16 Apr 2008 20:06:34 -0000 @@ -22,7 +22,8 @@ cd $TEMP /usr/bin/git clone git://git.fedorahosted.org/git/fedora-web.git > /dev/null 2>&1 cd fedora-web -/usr/bin/git checkout origin/live > /dev/null 2>&1 +# Checkout last F8 commit +/usr/bin/git checkout 091d53ea83b78e7a5ea2933be9100e74359802ee > /dev/null 2>&1
cd fedoraproject.org /bin/rm -rf /var/lib/puppet/application/fedoraproject.org/*
What do you think? Ricky
On Wed, 16 Apr 2008, Ricky Zhou wrote:
I'd like to update syncStatic.sh to enforce the website change freeze (in case I accidentally run make push). Here is the patch for the change:
Index: syncStatic.sh
RCS file: /cvs/puppet/configs/system/syncStatic.sh,v retrieving revision 1.20 diff -u -r1.20 syncStatic.sh --- syncStatic.sh 12 Dec 2007 23:11:07 -0000 1.20 +++ syncStatic.sh 16 Apr 2008 20:06:34 -0000 @@ -22,7 +22,8 @@ cd $TEMP /usr/bin/git clone git://git.fedorahosted.org/git/fedora-web.git > /dev/null 2>&1 cd fedora-web -/usr/bin/git checkout origin/live > /dev/null 2>&1 +# Checkout last F8 commit +/usr/bin/git checkout 091d53ea83b78e7a5ea2933be9100e74359802ee > /dev/null 2>&1
cd fedoraproject.org /bin/rm -rf /var/lib/puppet/application/fedoraproject.org/*
What do you think? Ricky
I think this is fine. Actually if you get a moment can you add this to our SOP under tickets to be filed so we do it automatically as part of the next release?
-Mike
On Wed, Apr 16, 2008 at 06:30:54PM -0500, Mike McGrath wrote:
On Wed, 16 Apr 2008, Ricky Zhou wrote:
I'd like to update syncStatic.sh to enforce the website change freeze (in case I accidentally run make push). Here is the patch for the change:
Index: syncStatic.sh
RCS file: /cvs/puppet/configs/system/syncStatic.sh,v retrieving revision 1.20 diff -u -r1.20 syncStatic.sh --- syncStatic.sh 12 Dec 2007 23:11:07 -0000 1.20 +++ syncStatic.sh 16 Apr 2008 20:06:34 -0000 @@ -22,7 +22,8 @@ cd $TEMP /usr/bin/git clone git://git.fedorahosted.org/git/fedora-web.git > /dev/null 2>&1 cd fedora-web -/usr/bin/git checkout origin/live > /dev/null 2>&1 +# Checkout last F8 commit +/usr/bin/git checkout 091d53ea83b78e7a5ea2933be9100e74359802ee > /dev/null 2>&1
cd fedoraproject.org /bin/rm -rf /var/lib/puppet/application/fedoraproject.org/*
What do you think? Ricky
I think this is fine. Actually if you get a moment can you add this to our SOP under tickets to be filed so we do it automatically as part of the next release?
How about making a tag on that commit so the script is readable? :-)
git tag -a fedora-8 091d53ea83b78e7a5ea2933be9100e74359802ee git checkout fedora-8
On 2008-04-16 10:13:47 PM, Matt Domsch wrote:
I think this is fine. Actually if you get a moment can you add this to our SOP under tickets to be filed so we do it automatically as part of the next release?
How about making a tag on that commit so the script is readable? :-)
git tag -a fedora-8 091d53ea83b78e7a5ea2933be9100e74359802ee git checkout fedora-8
Ah, good idea :) - that's done now (and mentioned on the release SOP).
Thanks, Ricky
On Thu, Apr 17, 2008 at 12:15:33AM -0400, Ricky Zhou wrote:
On 2008-04-16 10:13:47 PM, Matt Domsch wrote:
I think this is fine. Actually if you get a moment can you add this to our SOP under tickets to be filed so we do it automatically as part of the next release?
How about making a tag on that commit so the script is readable? :-)
git tag -a fedora-8 091d53ea83b78e7a5ea2933be9100e74359802ee git checkout fedora-8
Ah, good idea :) - that's done now (and mentioned on the release SOP).
Are you also making sure that the website content is getting copied out to the mirror space pub/fedora/web/ ? Perhaps less of a concern now that we have proxies scattered around the world, but the original thought was to have that content available on mirrors (30 or so are carrying it, and it's small, ~1MB) in case we needed to start redirecting at them in an emergency.
On 2008-04-16 11:32:08 PM, Matt Domsch wrote:
Are you also making sure that the website content is getting copied out to the mirror space pub/fedora/web/ ? Perhaps less of a concern now that we have proxies scattered around the world, but the original thought was to have that content available on mirrors (30 or so are carrying it, and it's small, ~1MB) in case we needed to start redirecting at them in an emergency.
I thought we agreed not to worry about getting it on the mirrors this time around (although I could be mistaken). If we do decide to do this, what would be the deadline for having the pages ready?
Thanks, Ricky
On Thu, 17 Apr 2008, Ricky Zhou wrote:
On 2008-04-16 11:32:08 PM, Matt Domsch wrote:
Are you also making sure that the website content is getting copied out to the mirror space pub/fedora/web/ ? Perhaps less of a concern now that we have proxies scattered around the world, but the original thought was to have that content available on mirrors (30 or so are carrying it, and it's small, ~1MB) in case we needed to start redirecting at them in an emergency.
I thought we agreed not to worry about getting it on the mirrors this time around (although I could be mistaken). If we do decide to do this, what would be the deadline for having the pages ready?
Yeah we kind of talked about it but I'm not sure if we came to a "total" conclusion. It's much less of a concern now since we actually have multiple sites to rely on. The last release didn't get anywhere close to needing to convert to a mirror site though I do like backup plans... -Mike
infrastructure@lists.fedoraproject.org
-
Matt Domsch -
Mike McGrath -
Ricky Zhou