Rawhide 20080404 Snapshot Released
by Jesse Keating
As part of our development schedule, we are releasing a snapshot of
Rawhide in Live form. We are releasing these via bittorrent
only as it is a much lighter weight method to get bits out the door than
to go through our mirroring system. If you cannot use bittorrent we
apologize for the inconvenience.
http://torrent.fedoraproject.org/ has a section marked
Rawhide-20080404-Snapshot with Live torrents. Due to ongoing issues
with X in anaconda we do not have CDs/DVDs of rawhide at this time. We
may add them if an X fix happens.
Please us bugzilla to report any problems you find (after making sure
that somebody else hasn't already reported the issues). The Beta
release notes ( http://fedoraproject.org/en/f9-beta-relnotes ) still
mostly apply.
Thanks for all the testing!
--
Jesse Keating
Fedora -- All my bits are free, are yours?
16 years, 1 month
[Guidelines Change] Even More Changes to the Packaging Guidelines
by Tom Callaway
In a special session this week, the Fedora Packaging Committee has
gotten even more changes done.
Specifically:
New guidelines describing how to package Java software can be found
here:
http://fedoraproject.org/wiki/Packaging/Java
*** This lifts the hold on Java Packages ***
New guidelines describing how to deal with GCJ compilation in Java
packages can be found here:
http://fedoraproject.org/wiki/Packaging/GCJGuidelines
New guidelines describing how to package Eclipse plugins can be found
here:
http://fedoraproject.org/wiki/Packaging/EclipsePlugins
New guidelines describing how to deal with SysV-style Initscripts can be
found here:
http://fedoraproject.org/wiki/Packaging/SysVInitScript
The Fedora Package Naming Guidelines have been updated to reflect the
new guidelines for package naming (EclipsePlugins). For details, please see:
http://fedoraproject.org/wiki/Packaging/NamingGuidelines
Also, the main Fedora Packaging Guidelines have been updated with links
to the new guidelines for specific package types (Java, EclipsePlugins), as
well as cleanups regarding Initscripts:
http://fedoraproject.org/wiki/Packaging/Guidelines
Last but not least, Scriptlet Snippets has been simplified to point to the
new SysVInitScript guidelines:
http://fedoraproject.org/wiki/Packaging/ScriptletSnippets
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC) and ratified by FESCo.
Many thanks to Andrew Overholt, Ville Skyttä, Thomas Fitzsimmons, Nicolas
Mailhot, all of the other Java helpers I've forgotten, and all of the members
of the FPC and FESCo, for assisting in drafting, refining, and passing these
guidelines.
A reminder: The Fedora Packaging Guidelines are living documents! If you
find something missing, incorrect, or in need of revision, you can
suggest a draft change. The procedure for this is documented here:
http://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure
Thanks,
~spot
16 years, 1 month
[Guidelines Change] Many Changes to the Packaging Guidelines
by Tom Callaway
Over the last month, the Fedora Packaging Committee has been busy adding
and amending the Fedora Packaging Guidelines.
Specifically:
New guidelines describing how to package OpenOffice.org extensions can
be found here:
http://fedoraproject.org/wiki/Packaging/OpenOffice.orgExtensions
New guidelines describing how to package Tcl/Tk addons can be found
here:
http://fedoraproject.org/wiki/Packaging/Tcl
The OCaml Packaging Guidelines have been updated:
http://fedoraproject.org/wiki/Packaging/OCaml
The Perl Packaging Guidelines have been significantly fleshed out:
http://fedoraproject.org/wiki/Packaging/Perl
The Fedora Package Naming Guidelines have been updated to reflect the
new guidelines for package naming (OpenOffice.org and Tcl/Tk). In
addition, all Fedora packages must be named using a specified subset of
ASCII characters. For details, please see:
http://fedoraproject.org/wiki/Packaging/NamingGuidelines
Also, the main Fedora Packaging Guidelines have been updated with links
to the new guidelines for specific package types (OpenOffice.org,
Tcl/Tk):
http://fedoraproject.org/wiki/Packaging/Guidelines
These guidelines (and changes) were approved by the Fedora Packaging
Committee (FPC)
and ratified by FESCo.
Many thanks to Caolan McNamara, Michael Thomas, Richard Jones, and all
of the members of the FPC and FESCo, for assisting in drafting,
refining, and passing these guidelines.
A reminder: The Fedora Packaging Guidelines are living documents! If you
find something missing, incorrect, or in need of revision, you can
suggest a draft change. The procedure for this is documented here:
http://fedoraproject.org/wiki/Packaging/Committee#GuidelineChangeProcedure
Thanks,
~spot
16 years, 1 month
Purging old Fedora test releases
by Jesse Keating
In order to make room for Fedora 9 and future releases, we are purging
all the old test releases on download.fedora.redhat.com. Both the Core
and post-Core test releases up to but not including Fedora 9 Beta.
The content has been archived internally at Red Hat and may one day show
up again for download on an archive site, but given that they were just
test releases that's not likely to happen.
--
Jesse Keating
Fedora -- All my bits are free, are yours?
16 years, 2 months
New bugzilla whiteboard tag - NeedsRetesting
by Jon Stanley
The QA and Bug Triage teams within Fedora are pleased to announce that
we have introduced a new tag to use within Bugzilla - NeedsRetesting.
Put this in the 'Status Whiteboard' field if you want the QA team to
test a resolution to your bug. There is a link to a query of all bugs
having this tag on http://fedoraproject.org/wiki/QA under 'Release
Testing'.
Ideally, bugs that have this keyword will not be hardware specific,
and should be hopefully) resolved, you just need confirmation. If
there is specific hardware required, then please make a note of it,
however, we cannot guarantee that any of the QA contributors actually
have any particular piece of hardware.
If you test one of these bugs, please remove the status whiteboard
field, such that the effort is not duplicated.
This is an effort to further drive quality in the project, and to keep
the bug counts manageable. Feel free to let me know if you have any
questions about this.
--
Jon Stanley
Fedora Bug Wrangler
jstanley(a)fedoraproject.org
16 years, 2 months
