12:23 a.m.
Hi,
According to http://fedoraproject.org/wiki/DocsProject/Schedule, on
the 1st of April, a "fedora-release-notes" package is sent to Fedora
release engineering. What exactly is this package? Is it something for
people to install?
Thanks,
Murray.
---------------------------------------------------------------------
pub 1024D/81B3FDEB 2007-09-19 [expires: 2008-09-18]
Key fingerprint = 4ED9 9907 5BF0 4132 2B46 20D1 C0C6 362D 81B3 FDEB
Murray McAllister (Fedora Docs Project / mdious) <murray.mcallister(a)gmail.com>
sub 2048g/B04CFA0C 2007-09-19 [expires: 2008-09-18]
8:52 a.m.
On Thu, 2008-03-20 at 15:23 +1000, Murray McAllister wrote:
Hi,
According to http://fedoraproject.org/wiki/DocsProject/Schedule, on
the 1st of April, a "fedora-release-notes" package is sent to Fedora
release engineering. What exactly is this package? Is it something for
people to install?
That's correct. Once all the translations are done and we have the PO
files in hand, we run "make release-srpm" in release-notes/devel/ .
This downloads the current CVS HEAD of some other modules: about-fedora,
homepage, readme-burning-isos, readme-live-image, and readme.
From each of these modules we build the required files in all languages
marked in those modules (via their individual po/LINGUAS files, same as
many other applications). We also build the release notes in HTML, and
then make a great big tarball out of everything.
That tarball is imported into the Fedora Package CVS repository, as a
source tarball for that RPM, the same way a package maintainer would do
for any package. (We also maintain a specfile in our CVS that is copied
to the Fedora Package CVS. That's where we do testing of new tool stuff
before we start messing with the "real" package CVS.
Once in the Fedora Package CVS, the package is built by the normal
packager toolchain (through koji and bodhi, and tagged for the distro)
just like any other package. The fedora-release-notes package is
required by the fedora-release package, so it ends up on pretty much all
systems.
To test or build the 'release-srpm' target, you need to have the
"Authoring and Publishing" group and the "w3m" package installed via
yum.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
4:39 p.m.
On Thu, Mar 20, 2008 at 11:52 PM, Paul W. Frields <stickster(a)gmail.com> wrote:
On Thu, 2008-03-20 at 15:23 +1000, Murray McAllister wrote:
> Hi,
>
> According to http://fedoraproject.org/wiki/DocsProject/Schedule, on
> the 1st of April, a "fedora-release-notes" package is sent to Fedora
> release engineering. What exactly is this package? Is it something for
> people to install?
That's correct. Once all the translations are done and we have the PO
files in hand, we run "make release-srpm" in release-notes/devel/ .
This downloads the current CVS HEAD of some other modules: about-fedora,
homepage, readme-burning-isos, readme-live-image, and readme.
From each of these modules we build the required files in all languages
marked in those modules (via their individual po/LINGUAS files, same as
many other applications). We also build the release notes in HTML, and
then make a great big tarball out of everything.
That tarball is imported into the Fedora Package CVS repository, as a
source tarball for that RPM, the same way a package maintainer would do
for any package. (We also maintain a specfile in our CVS that is copied
to the Fedora Package CVS. That's where we do testing of new tool stuff
before we start messing with the "real" package CVS.
Once in the Fedora Package CVS, the package is built by the normal
packager toolchain (through koji and bodhi, and tagged for the distro)
just like any other package. The fedora-release-notes package is
required by the fedora-release package, so it ends up on pretty much all
systems.
To test or build the 'release-srpm' target, you need to have the
"Authoring and Publishing" group and the "w3m" package installed
via
yum.
Thanks!
So when fedora-release-notes is installed, does that mean people can
view them by going System -> Documentatoin -> [something]?
If this is the case, will this be on the Fedora 9 beta desktop?
Cheers,
Murray.
---------------------------------------------------------------------
pub 1024D/81B3FDEB 2007-09-19 [expires: 2008-09-18]
Key fingerprint = 4ED9 9907 5BF0 4132 2B46 20D1 C0C6 362D 81B3 FDEB
Murray McAllister (Fedora Docs Project / mdious) <murray.mcallister(a)gmail.com>
sub 2048g/B04CFA0C 2007-09-19 [expires: 2008-09-18]
4:52 p.m.
On Fri, 2008-03-21 at 07:39 +1000, Murray McAllister wrote:
On Thu, Mar 20, 2008 at 11:52 PM, Paul W. Frields
<stickster(a)gmail.com> wrote:
> On Thu, 2008-03-20 at 15:23 +1000, Murray McAllister wrote:
> > Hi,
> >
> > According to http://fedoraproject.org/wiki/DocsProject/Schedule, on
> > the 1st of April, a "fedora-release-notes" package is sent to
Fedora
> > release engineering. What exactly is this package? Is it something for
> > people to install?
>
> That's correct. Once all the translations are done and we have the PO
> files in hand, we run "make release-srpm" in release-notes/devel/ .
> This downloads the current CVS HEAD of some other modules: about-fedora,
> homepage, readme-burning-isos, readme-live-image, and readme.
>
> From each of these modules we build the required files in all languages
> marked in those modules (via their individual po/LINGUAS files, same as
> many other applications). We also build the release notes in HTML, and
> then make a great big tarball out of everything.
>
> That tarball is imported into the Fedora Package CVS repository, as a
> source tarball for that RPM, the same way a package maintainer would do
> for any package. (We also maintain a specfile in our CVS that is copied
> to the Fedora Package CVS. That's where we do testing of new tool stuff
> before we start messing with the "real" package CVS.
>
> Once in the Fedora Package CVS, the package is built by the normal
> packager toolchain (through koji and bodhi, and tagged for the distro)
> just like any other package. The fedora-release-notes package is
> required by the fedora-release package, so it ends up on pretty much all
> systems.
>
> To test or build the 'release-srpm' target, you need to have the
> "Authoring and Publishing" group and the "w3m" package
installed via
> yum.
>
Thanks!
So when fedora-release-notes is installed, does that mean people can
view them by going System -> Documentatoin -> [something]?
If this is the case, will this be on the Fedora 9 beta desktop?
Yes, it has been and is.
If you go to System -> Help you can see the Release Notes on the front
page. If you use KDE it's also on the help menu. We've had this
since... FC-6, I think.
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
5881
days inactive
5881
days old
3 comments
2 participants
participants (2)
-
Murray McAllister -
Paul W. Frields