脚本的作者是 Dan Berrange，我(Richard Jones)做了修改。我们在打包 MinGW 和 OCaml 过程中已经用了很久了。

根据 Seth Vidal，这个脚本的功能可能将被整合到 mock 中。

原文见 ANNOUNCE: Smock (simpler mock) – a mock wrapper for chain building

‘Smock’ stands for ‘simpler mock’. It’s a script that runs on top of
mock, allowing you to chain-build a series of RPMs from a single
command.
smock.pl --arch=i386 --arch=x86_64 \
--distro=fedora-9 --distro=fedora-10 \
*.src.rpm

The above command would arrange the SRPMs into the correct order
according to their BuildRequires, then build each in the four separate
mock environments Fedora {9,10} {i386,x86_64}. It makes the result of
each previous package build available to subsequent packages, and in
case of error it is fully restartable (it skips packages which have
already been built).

The script was written by Dan Berrange and extensively hacked on by
me. This is how we've been building the MinGW & OCaml packages for
quite a while.

Available from:

http://hg.et.redhat.com/misc/fedora-mingw--devel/

(click 'manifest' then 'smock')

Please read the README file!

Example output:

http://www.annexia.org/tmp/mingw/fedora-9/

Example wrapper script we use for MinGW:

http://hg.et.redhat.com/misc/fedora-mingw--devel/?f=d3dc6fa7cddd;file=build-everything-in-mock.sh

Commands we use for OCaml:

cd fedora
for f in ocaml*; do (cd $f/devel && make srpm); done
smock.pl --arch=i386 --arch=x86_64 --distro=fedora-rawhide \
ocaml*/devel/*.src.rpm

Rich.

Fedora 11 非常重要，因为它将是 RHEL 6 的基础。如果将 Fedora 11 推迟一个月，而不是照常的五月一日发布，可以带来更完整的 feature 内容；但是 Fedora 12 如果需要保证十月三十日发布，其中的 feature 就会比较少。这样是否可以接受？

原文见 Fedora 11 schedule proposal

We (Fedora Release Engineering) would like to propose a schedule for
F11. The reason I’m bringing this to F-A-B is that it is a departure
from our typical May1/Oct31 release dates. This is due to the month~
delay that Fedora 10 has had already due to the break in.

Before I get to the schedule itself, I want to explain where we are
coming from, and what some of the drivers for this schedule are.

Fedora releases typically have a 6 month development cycle. We target
specific dates for the release to give developers, end users, and
upstreams a target to shoot for. Typically any slipping of a release we
do, we just shorten the next release to make up for it. However a
month’s time is quite a lot to shrink. Especially because of the
significance of F11.

Fedora 11 will be extremely important to Red Hat Enterprise Linux
(otherwise known as RHEL). RHEL 6 planning has looked to use Fedora 10
and Fedora 11 as releases to work out new technologies and features that
are desired in RHEL 6. This includes a lot of upstream work that is
being done, and targeted to land in these two releases. That planning
was also planning for a full 6 month Fedora 11 cycle, and Red Hat
resources were lined up to take advantage of this, by participating more
in the development cycle, in the testing cycle, in bugfixing, etc…
This is a good thing.

However, if we were to take a month out of Fedora 11s schedule to hit
that May 1 date, we would shorten the amount of time we get the RH
attention, and we shorten the amount of time we give our developers to
land the pre-planned features. This is not a good thing. These are not
just RH developers for RH features either, it’s all developers for all
features.

But wait, if we pad Fedora 11 by a month, what about Fedora 12?
Excellent question. We (releng) feel that if we set up Fedora 11 with a
full 6 month schedule, and now set up F12 to take in some of that slip
and shoot for Oct 31 release of F12, all interested parties will have a
lot more time to prepare for a short release. In fact, we could even
focus more on polish issues in F12 than large sweeping features, but I
leave that up to the developers. We just feel that we can better plan
for a short release in the F12 time frame than we can in the F11 time
frame, and by doing so we can get back to our May 1, Oct 31 established
dates which work pretty well in the Linux ecosystem. Of course, setting
an F12 schedule now would be kind of silly given that we don’t know what
will happen during F11 (hey, look at what happened to F10!), but we can
at least have an idea of what we’d like to do in F12.

Long story short, here is a simple schedule we’d like to present for
F11. http://fedoraproject.org/wiki/TomCallaway/F11ProposedSchedule

Note that it is pretty basic, only a few dates are called out. Also
those dates are somewhat subject to change. We’re mostly interested in
the end date of Tuesday May 26th. The intra-schedule dates are given
mostly for reference, and we’ll still need to spend some time vetting
them against trade shows, holidays, etc… We’ll also be filling in all
the other details that you typically see in a Fedora schedule, once we
reach an agreed upon strategy for F11/F12.

I’d like to see some conversation on this (or none if you all agree with
me) and a conclusion met within the next 2 weeks, that is at or before
the release of Fedora 10.

Thank you for your time and thoughts.

–
Jesse Keating
Fedora — Freedom² is a feature!

本邮件的用意是希望通过讨论，找到两个 Wiki 页面尚未涉及的方面。最终的目标则是达成一致，得到 Board 和 FESCo 批准的规则，由定制版小组执行。

原文见 Spins process – technical requirements

A little while ago, a few of us had a meeting via phone[1] discussing
the spins process for F11. One of my action items from that meeting
was to come up with a list of technical requirements for Spins. The
Spins SIG already had some up[2], so for the most part, I didn’t see a
need to go reinventing the wheel. There is some overlap between my
(woefully incomplete, mostly because I envision it being integrated
into the existing page) draft[3] and the existing process.

This is intended to start a discussion of what other technical
requirements that there are beyond those which are in either of the
two wiki pages. The end goal is to have something that is approved by
both the Board and FESCo, and executed by the Spins SIG.

[1] http://www.redhat.com/archives/fedora-devel-list/2008-October/msg00087.html
[2] http://fedoraproject.org/wiki/SIGs/Spins/CommunitySpinGuidelines
[3] https://fedoraproject.org/wiki/User:Jstanley/SpinsTechRequirements

原文见 Mass ACL open complete

The mass ACL open has at last been completed. If you did not opt out of this change in pkgdb, your package is now open to all of the uber^H^Hprovenpackager group. The checkbox to opt in or out may still be present, but is no longer useful and should go away very shortly.

–CJD

在实际分支过程中，由于 CVS 邮件发送被禁用，CVS 将有一段时间下线。这段时间内我们不希望有任何修改被提交。CVS 下线从周五(2008-11-07) 03:00 UTC 开始。我们不知道需要下线多久，不过(由于 packagedb 的改进)，相比过去的大规模分支，时间将缩短许多。

如果计划有变更将另行通知。正式下线之前还将有另一个通知。任何问题请到 #fedora-admin 说话。

原文见 CVS mass-branching coming soon

On Thursday of this week we will be mass branching CVS for F-10. I
realize that this is a bit late, however it is the earliest we are
comfortable doing it given changes in pkgdb to facilitate the branching.

There will be an outage of CVS during the actual branching due to
disabling email delivery of cvs changes during the branching. We don’t
want any changes sneaking in during that time. This outage is scheduled
to begin at 0300 UTC Friday Nov 7th.

Unfortunately we do not have a good estimate as to how long the outage
will last, however it should be much much quicker than previous outages
for mass branching.

If any plans change before now and then we will announce them, as well
as announce a reminder just prior to the outage.

Any questions can be asked on fedora-devel-list or #fedora-admin on
Freenode IRC.

–
Jesse Keating
Fedora — Freedom² is a feature!

所有打破冻结的软件包和包含在最终发布中的包都包含在 buildroot 中。

dist-f10 标签已被锁定，新的 build 不会被自动标记。如果你遇到由于锁定的标签引起的 build 失败，请联系 releng 或自己修改标签：
# koji tag-pkg dist-f10-updates-candidate

原文见 F10 builds targetted for dist-f10-updates-candidate

In order to properly prepare F10 updates, all F10 builds are now
targetted at dist-f10-updates-candidate. This is a setting in the
‘common’ directory of your package modules, so you’ll want to make sure
you’re using an up to date common.

The buildroot for dist-f10-updates-candidate is comprised of dist-f10
content, which means builds done in dist-f10-updates-candidate
will /not/ automatically be usable in the buildroot. You’ll need to
request a buildroot override in order to do build sets.

Also, any build that we break the freeze for and tag for Fedora 10
release will also be available in the buildroot.

I have locked the dist-f10 tag so that no more builds can automatically
get tagged. If you have a build that fails due to a locked tag, you can
either ping releng, or manually tag it yourself for
dist-f10-updates-candidate:

# koji tag-pkg dist-f10-updates-candidate
–
Jesse Keating
Fedora — Freedom² is a feature!

如果你做 build 是为了修正 bug，请确保在最终发布前将你的 build 打上适合的标记。可以到 koji 中看标记为 “f10-final” 标记的软件包和 build。凡是带有 f10-final 标记的软件包和 build 才用来创建最终发布。最终发布前的 rawhide 也只会包含这些内容。也可以执行
koji latest-pkg f10-final
让我们把最后的路程顺利走完！

原文见 Frozen for Fedora 10

Last night at 0555 UTC we froze for Fedora 10. The rawhide from
20081028 is the frozen content. At this point, builds for F10 are not
automatically brought into Rawhide, and won’t be in the Fedora 10
release. To request a freeze override, please use the Final Freeze
Policy[1]

If you’re closing bugs by doing builds, please ensure that those builds
get properly tagged for our final release.

To check the status of your particular build/package, you can look at
the contents of the ‘f10-final’ tag in Koji. This is the tag for the
Fedora 10 release, and what rawhide will compose from until F10 is done.

koji latest-pkg f10-final

It’s the last mile folks, lets make it awesome!

[1]: https://fedoraproject.org/wiki/ReleaseEngineering/FinalFreezePolicy
–
Jesse Keating
Fedora — Freedom² is a feature!

原文见 Translation packagers: Rebuild before devel freeze

Reminding maintainers of Fedora-translatable packages to issue a build
before the Development Freeze of tomorrow, 28/10, in order to have all
translations submitted until the translation deadline of 21/10
included in Fedora 10 (otherwise our translator’s hard work will go to
the gutter). If you haven’t received any translations since the last
build, a rebuild is not necessary.

Feel free to drop an email to fedora-trans-list redhat com if you have
any questions.

Thanks for caring for translations*. (=

-δ

*and, subsequently, 60%+ of our users.

–
Dimitris Glezos

阻碍 Fedora 10 发布的 Bug 列表为 https://bugzilla.redhat.com/showdependencytree.cgi?id=438943&hide_resolved=1
待审核的 Fedora 10 Bug 列表为 https://bugzilla.redhat.com/showdependencytree.cgi?id=446449&hide_resolved=1
另外还有大约 600 个 Bug 未经分拣，也可能成为发布的阻碍，需要一并考虑 http://tinyurl.com/6llac8
最后，所有其他列表见 https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers

原文见 Blocker Bug Review Meeting :: Monday @ 14:00 UTC

A meeting is being held to review the current blocker bugs in anticipation of the Final Development Freeze this Tuesday, October 28th.

All teams (thus the cc to f-a-b) in Fedora are welcome to join in and help.

WHEN: Monday, October 27, 2008 @ 14:00 UTC (10 AM EDT) and going as long as we need to

WHERE: irc.freenode.net #fedora-blocker

Fedora 10 Blocker: https://bugzilla.redhat.com/showdependencytree.cgi?id=438943&hide_resolved=1 Fedora 10 Preview Blocker: https://bugzilla.redhat.com/showdependencytree.cgi?id=446449&hide_resolved=1

There still remain approximately 600 rawhide bugs that have not been triaged for potential blocker status and should be considered as well. These bugs are here: http://tinyurl.com/6llac8

Other tracker bugs of interest are here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Trackers

John

最终冻结日未标为 100% 的页面将于周三(2008-10-29)提交 FESCo 审核。

原文见 Features & Final Development Freeze

If all goes as planned, the final development freeze will arrive a week
from Tuesday on October 28, 2008.

Final Development Freeze, defined here:
http://fedoraproject.org/wiki/ReleaseEngineering/FinalFreezePolicy means
that all features and their associated feature pages must be at 100%
completion by this date. The following features pages do not currently
meet this criteria and should by updated by October 28, 2008:

https://fedoraproject.org/wiki/Features/BetterStartup

https://fedoraproject.org/wiki/Features/BetterWebcamSupport

https://fedoraproject.org/wiki/Features/EchoIconTheme

https://fedoraproject.org/wiki/Features/EFI

https://fedoraproject.org/wiki/Features/KernelModesetting

Yes, we know “this is Fedora” and “stuff is never 100% done” and all the
usual arguments about “what does percentage completion really mean,
etc., etc.” However, for the average user and members of the other
Fedora teams it is important and very helpful to make one last update to
your feature page to make it reflect everything that was completed for
Fedora 10. The things that weren’t completed should be removed or
clearly labeled as slated for a future release.

Feature pages not updated and at 100% will be raised to FESCo on October
29, 2008.

Thanks,
John