One thing we'd been talking about before the freeze but just didn't get
around to was giving steved (nfs expert) access to our nfs box where
/mnt/koji lives as we still seem to be having nfslock issues (though they
are less frequent now).
This is mostly so A) he can see how things are setup before an outage and
B) get immediate access to see what happened during the outage.
I'd like to get his account on there (and possibly xen2 if he needs it)
before the freeze so we can keep the outage time to a minimum and possibly
have a fix right then or at least have a fix after the change freeze
Anyone opposed? The only change here is actually giving steved access to
the boxes (with sudo) any other changes will have to come back through the
list when we have them.
PS. This isn't in an SOP but if nfslock happens on nfs1 and steved isn't
around. Anyone in sysadmin-main can just reboot the box which will cause
a quick down time but we've yet to figure out how to bring nfslock back up
sanely without the reboot.
So xen1 went down today and I was helping bring things back up. I didn't
know to look in /var/log/messages for the messages from
xenGuestsRunning.sh. I was wondering this:
would it make sense to have xenGuestsRunning run every hour and re-make
the symlinks in /etc/xen/auto for the guests which should be running on
the machine? Also - if for some reason the xen guests can't be started
up automatically due to other complexities (iscsi, memory over commit,
etc) we could have xenGuestsrunning auto-generate a script which can be
run to re-make the xen guests which should be running.
I'd be willing to put the script together, I just wanted to ask if there
was a good reason NOT to do this, so I don't waste time if I've missed
I only speak for me.
Since we're back to more invasive changes I'd like to install the rhel 5.2
beta kernel on xen1 and reboot it. It died today and I suspect this is
because of iscsi issues we've seen before (rare, but still happening)
Looks like the release slipped meaning the new date is currently on May
Jesse, with your blessing I'd like to remove the change freeze window and
start it back up again on April 29th, to end on May 14th. Sound good?
At today's regularly scheduled meeting, the Fedora Engineering
Steering Committee (FESCo) decided that Fedora 9 release will be
slipping by exactly two weeks.
Because of other slippage, coupled with some technical difficulties
during this previous week, our Preview Release was unexpectedly
stalled. The Preview Release is where we expect to catch all manner
of last-minute bugs, do very heavy QA, and otherwise perform all the
final spit-and-polish. There needs to be sufficient time between the
PR and the release for testers to find and report issues.
There are less than two weeks remaining until the original target date
of April 29th. About a week before that date we have to have
everything locked and loaded for distribution by our mirrors. That
small a timeframe would then make the Preview Release -- normally a
very important part of our release schedule -- nearly useless.
This slip is not intended to make room for more changes, it is only
intended to make room for fixing the things we already know about, and
allowing new things to be found, and evaluated as release blocking, and
fixed. There are also a fair number of bugs we think we've already
fixed, but need wider audience testing to be sure.
The current blocker list is viewable at
https://bugzilla.redhat.com/showdependencytree.cgi?id=235706&hide_resolved=1 however since there is nothing preventing people from adding bugs to this list it will get culled from time to time from things that aren't actually blockers. A (rather longer) list of things we'd like to see fixes for can be seen https://bugzilla.redhat.com/showdependencytree.cgi?id=235705&hide_resolved=1 although this list does get less attention than the blocker list.
We deeply appreciate the value we get from our community in using our
development tree and testing our release attempts. Without your input,
our releases couldn't possibly be as good as they have been. Please
help us use these extra couple of weeks to make the already awesome
Fedora 9 even better!
Fedora -- All my bits are free, are yours?
Fedora-devel-announce mailing list
(01:03:22 PM) abadger1999 has changed the topic to: Fedora
(01:03:42 PM) abadger1999: Alrighty! Meeting starting
(01:03:48 PM) gkrpan: <-- here
(01:04:06 PM) ivazquez: Present.
(01:04:17 PM) ***iWolf lurks
(01:04:18 PM) wolfy left the room ("Make every day good to the last
drop.. nobody gets out alive in the end anyway!").
(01:04:46 PM) abadger1999: f13: ping
(01:05:24 PM) abadger1999: We don't have too much today.
(01:05:32 PM) abadger1999: Change Freeze is in effect.
(01:05:32 PM) f13: pong
(01:05:55 PM) abadger1999: So remember if you have a change you need
please email the list before making it live.
(01:06:32 PM) abadger1999: f13: Could you give us a summary of FESCo's
meeting today and what things we need to be watching in Infrastructure?
(01:06:57 PM) abadger1999 has changed the topic to: Fedora
Infrastructure: FESCo, release, etc
(01:07:12 PM) f13: FESCo decided to introduce a 2 week slip of the
Fedora 9 schedule
(01:07:44 PM) f13: this is mostly to allow Preview Release some time to
be consumed and gather reports back, and also to take into account that
a good chunk of X team is out this week and some of next at a
conference, and I'm out the last week of April
(01:07:59 PM) f13: nothing other than dates should really change for
(01:08:27 PM) abadger1999: Sounds good.
(01:09:28 PM) f13: PReview Release is about to be made available via
(01:09:43 PM) f13: and I'm going to also stage it for mirrors so that we
can offer jigdo
(01:09:52 PM) f13: that will be made available early next week
(01:10:15 PM) abadger1999: What is the new release date going to be?
(01:10:41 PM) f13: May 13
(01:11:39 PM) abadger1999: Okay. We'll need to update the counter on
(01:12:17 PM) abadger1999: and extend the freeze. (possibly shorten on
this end, possibly not.)
(01:12:40 PM) abadger1999: Anyone else have questions?
(01:13:03 PM) abadger1999: f13: Thanks for the update!
(01:13:13 PM) f13: np, I have to run for a bit
(01:13:22 PM) abadger1999 has changed the topic to: Fedora
Infrastructure Meeting: Tickets
(01:13:32 PM) abadger1999: Okay, we only a have a few meeting tickets
(01:13:40 PM) abadger1999: jcollie: ping?
rahul_b rdieter RenaultR83 ricky rsc
rahul_b rdieter RenaultR83 ricky rsc
(01:14:28 PM) RenaultR83 left the room (quit: Connection timed out).
(01:14:40 PM) RenaultR83
[n=couretca(a)AToulon-151-1-7-46.w83-197.abo.wanadoo.fr] entered the room.
(01:15:29 PM) abadger1999: Okay. So no update on audio conferencing via
(01:15:55 PM) abadger1999: .ticket 398
(01:15:57 PM) zodbot: abadger1999: #398 (elfutils `monotone' (mtn)
error) - Fedora Infrastructure - Trac -
(01:16:20 PM) abadger1999: The monotone bug has been up for a while. I
noticed that the upstream bug has a link to a program thatmight help.
(01:17:01 PM) abadger1999: I've asked rmcgrath to evaluate whether usher
will do what we need.
(01:17:14 PM) abadger1999: .ticket 446
(01:17:15 PM) zodbot: abadger1999: #446 (Possibility to add external
links on spins page) - Fedora Infrastructure - Trac -
(01:17:45 PM) abadger1999: It looks like we need to find a good way to
link to the external spins that people are producing.
(01:18:07 PM) yingbull [n=yingbull(a)S01060013104275dd.ss.shawcable.net]
entered the room.
(01:18:22 PM) abadger1999: There's likely to be quite a few which are
localizations of the main Fedora Spin.
(01:18:31 PM) ***yingbull arrives.
(01:18:58 PM) abadger1999: Hey yingbull
(01:19:16 PM) abadger1999: Does websites control spins.fp.o?
(01:19:48 PM) abadger1999: How do they feel about designing something to
link to external spins? Better to have a link to the wiki as dgilmore
(01:20:15 PM) abadger1999: ricky, ivazquez: Thoughts?
(01:21:13 PM) ivazquez: Restricting the links on the page to internal
torrents does simplify things, but not by a lot. Personally I have no
preference for or against.
(01:21:25 PM) mdomsch [n=Matt_Dom(a)cpe-70-124-62-55.austin.res.rr.com]
entered the room.
(01:22:01 PM) Stalwart left the room (quit: Connection timed out).
(01:22:23 PM) abadger1999: mdomsch: The logs so far:
(01:23:15 PM) tibbs left the room (quit: "Konversation terminated!").
(01:23:18 PM) abadger1999: Okay. So if we put them into the page
directly we need to have people get the information to you to update the
(01:23:30 PM) abadger1999: Does a ticket work best for that?
(01:24:12 PM) ivazquez: Well, having said that, the infrastructure for
supporting "off-site" spins isn't in place.
(01:24:38 PM) abadger1999: Ah. Okay. So let's put this on hold until
mmcgrath can fill in some of the blanks.
(01:24:48 PM) ivazquez: Currently it uses the original page-generation
script which I don't believe can handle that.
(01:25:25 PM) ivazquez: (and I admittedly don't know enough about FI to
poke at it)
(01:25:45 PM) abadger1999: Alrighty.
(01:25:56 PM) abadger1999 has changed the topic to: Fedora Infrastruture
Meeting: Open Floor
(01:26:10 PM) abadger1999: Anyone have any topics to discuss?
(01:28:33 PM) abadger1999: I have one: With the two week slip of the
release, we need to extend the change freeze.
(01:28:58 PM) abadger1999: So, May 14th as the end date.
(01:29:58 PM) abadger1999: Sound reasonable? Should we cut a bit off
this end as well or has the burden not been to onerous on people?
(01:30:18 PM) mdomsch: and we don't unfreeze now
(01:30:55 PM) ivazquez: Do we want to be frozen for an entire month?
(01:32:09 PM) ivazquez: Okay, I'm not hearing any one arguing that we
shouldn't, so I'll live.
(01:32:50 PM) ***abadger1999 notes that he doesn't care
(01:33:08 PM) lmacken: sounds reasonable to me.
(01:33:15 PM) lmacken: even though i'll probably have to break freeze
for bodhi at some point :\
(01:33:38 PM) abadger1999: The change freeze was supposed to start two
weeks before release. So if we unfreeze we'd push it back to Apr 29.
(01:34:12 PM) abadger1999: If we stay frozen, we could be much more
liberal with what we accept until that date... but then, what's the
purpose of the freeze then?
(01:34:16 PM) mdomsch: freeze + exceptions is sane
(01:34:28 PM) mdomsch: just get exceptions reviewed
(01:35:50 PM) bpepple left the room (quit: Read error: 110 (Connection
(01:35:53 PM) abadger1999: Okay. So proposal: Announce changes to the
list. Reviewers know that we can continue to make more intrusive
changes until Apr 29. So be liberal with the +1's until then.
(01:37:51 PM) ivazquez: That seems acceptable to me.
(01:38:02 PM) abadger1999: Alright.
(01:38:05 PM) yingbull: Sounds fine by me, too.
(01:38:42 PM) abadger1999: Oh one more announcement: f13 and I will be
finalizing a plan for mass branching of cvs and branching this weekend.
(01:39:26 PM) abadger1999: That means an outage for cvs commits. We'll
send mail to fedora-devel-announce about that.
(01:39:33 PM) abadger1999: Anyone else have anything?
(01:39:52 PM) mdomsch: f13 just sent the announcement; I'll forward to
(01:42:26 PM) abadger1999: Okay. I'll close the meeting in 60
(01:42:52 PM) RenaultR83 left the room (quit: Read error: 110
(Connection timed out)).
(01:44:22 PM) bpepple
[n=bpepple(a)adsl-76-228-104-62.dsl.wotnoh.sbcglobal.net] entered the room.
(01:46:28 PM) jwb is now known as jwb_gone
(01:46:37 PM) abadger1999: Okay.Thanksall
(01:46:49 PM) abadger1999 has changed the topic to: Topic for
#fedora-meeting is Channel is used by various Fedora groups and
committees for their regular meetings | Note that meetings often get
logged | For questions about using Fedora please ask in #fedora | See
I have been contributing with Fedora Project for years, mainly as Ambassador
and Translator. Now, I'm running around the web development. Currently I'm
working on some Transifex enhancements and that drives me to be the newest
member of Fedora Infrastructure Projetc.
I'm glad to be here! ;)
Diego Búrigo Zacarão
Linux User #402589
USE SOFTWARE LIVRE
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
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 @@
/usr/bin/git clone git://git.fedorahosted.org/git/fedora-web.git >
-/usr/bin/git checkout origin/live > /dev/null 2>&1
+# Checkout last F8 commit
+/usr/bin/git checkout 091d53ea83b78e7a5ea2933be9100e74359802ee >
/bin/rm -rf /var/lib/puppet/application/fedoraproject.org/*
What do you think?