Hi,
Who is responsible for building the release notes RPM for the 1st of April?
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@gmail.com sub 2048g/B04CFA0C 2007-09-19 [expires: 2008-09-18]
On Tue, 2008-03-25 at 11:18 +1000, Murray McAllister wrote:
Hi,
Who is responsible for building the release notes RPM for the 1st of April?
Cool Murray, thanks for volunteering!
:-)
Seriously though, this is part of the release-notes process and we'll help you (and any other interested people) through it. Interesting because it actually involves other modules on which we haven't done much (maybe enough) work recently.
The about-fedora module is reasonably general so it doesn't require change very often. The readme, readme-burning-isos, and readme-live-image modules might be less so. Anyone care to take a look at them and see if there's anything worth fixing before we send out the final POT for the F9 "gold" release in a couple weeks?
On Tue, Mar 25, 2008 at 11:54 AM, Paul W. Frields stickster@gmail.com wrote:
On Tue, 2008-03-25 at 11:18 +1000, Murray McAllister wrote:
Hi,
Who is responsible for building the release notes RPM for the 1st of April?
Cool Murray, thanks for volunteering!
:-)
Hah!
I'll start practicing building the RPMs now. Do you run "make release-srpm", or should it be...."make omf"?
Seriously though, this is part of the release-notes process and we'll help you (and any other interested people) through it. Interesting because it actually involves other modules on which we haven't done much (maybe enough) work recently. The about-fedora module is reasonably general so it doesn't require change very often. The readme, readme-burning-isos, and readme-live-image modules might be less so. Anyone care to take a look at them and see if there's anything worth fixing before we send out the final POT for the F9 "gold" release in a couple weeks?
-- 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
--
Thanks very much for your help so far!
Regards,
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@gmail.com sub 2048g/B04CFA0C 2007-09-19 [expires: 2008-09-18]
On Tue, 2008-03-25 at 12:21 +1000, Murray McAllister wrote:
On Tue, Mar 25, 2008 at 11:54 AM, Paul W. Frields stickster@gmail.com wrote:
On Tue, 2008-03-25 at 11:18 +1000, Murray McAllister wrote:
Hi,
Who is responsible for building the release notes RPM for the 1st of April?
Cool Murray, thanks for volunteering!
:-)
Hah!
I'll start practicing building the RPMs now. Do you run "make release-srpm", or should it be...."make omf"?
It will be 'make release-srpm', but don't expect it to work right away -- it's very dependent on translators to have finished their work. When they're done, we usually have to tweak some of the modules' po/LINGUAS files to keep errant locales from breaking the build if we can't fix them ourselves.
On Tue, Mar 25, 2008 at 12:28 PM, Paul W. Frields stickster@gmail.com wrote:
On Tue, 2008-03-25 at 12:21 +1000, Murray McAllister wrote:
On Tue, Mar 25, 2008 at 11:54 AM, Paul W. Frields stickster@gmail.com wrote:
On Tue, 2008-03-25 at 11:18 +1000, Murray McAllister wrote:
Hi,
Who is responsible for building the release notes RPM for the 1st of April?
Cool Murray, thanks for volunteering!
:-)
Hah!
I'll start practicing building the RPMs now. Do you run "make release-srpm", or should it be...."make omf"?
It will be 'make release-srpm', but don't expect it to work right away -- it's very dependent on translators to have finished their work. When they're done, we usually have to tweak some of the modules' po/LINGUAS files to keep errant locales from breaking the build if we can't fix them ourselves.
Thanks for your help.
Looking at the schedule (http://fedoraproject.org/wiki/DocsProject/Schedule):
* 31 March 2008: PO files due from L10N
Preview Release translation & development freeze
1 April 2008: fedora-release-notes package PR to Fedora release engineering
Is this by April 1, or can it be UTC 2359 April 1?
Do I have to do anything more, other than build it, and check it back into CVS?
What happens if a translation messes up the build? Is there time for the translator to fix it?
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@gmail.com sub 2048g/B04CFA0C 2007-09-19 [expires: 2008-09-18]
On Sun, Mar 30, 2008 at 4:12 AM, Murray McAllister murray.mcallister@gmail.com wrote:
Looking at the schedule (http://fedoraproject.org/wiki/DocsProject/Schedule):
- 31 March 2008: PO files due from L10N
Preview Release translation & development freeze
1 April 2008: fedora-release-notes package PR to Fedora release engineering
Is this by April 1, or can it be UTC 2359 April 1?
All times listed on our schedules are always UTC 2359 on the listed date. So if you're looking for that extra time, it's there! :-)
Do I have to do anything more, other than build it, and check it back into CVS?
Just the building, but I will probably need to be around to help you with that, in case something goes awry.
What happens if a translation messes up the build? Is there time for the translator to fix it?
Not really, but sometimes the errors are simple, like a mistyped XML tag, meaning we can fix them ourselves. (You have to use a decent PO-aware tool, like... oh, Emacs! Gosh, is there nothing it can't do?) :-)
In cases where the problem is *really* egregious, we have to disable the translation in question and notify the translator so they can fix it before GA. That rarely happens -- except when translators fail to translate the entities in docs-common, but in that case we can simply enter empty PO files and build anyway, notifying the translators of the need to take care of it in the next few weeks.
Paul
On Mon, Mar 31, 2008 at 9:40 AM, Paul Frields stickster@gmail.com wrote:
On Sun, Mar 30, 2008 at 4:12 AM, Murray McAllister murray.mcallister@gmail.com wrote:
Looking at the schedule (http://fedoraproject.org/wiki/DocsProject/Schedule):
- 31 March 2008: PO files due from L10N
Preview Release translation & development freeze
1 April 2008: fedora-release-notes package PR to Fedora release engineering
Is this by April 1, or can it be UTC 2359 April 1?
All times listed on our schedules are always UTC 2359 on the listed date. So if you're looking for that extra time, it's there! :-)
Do I have to do anything more, other than build it, and check it back into CVS?
Just the building, but I will probably need to be around to help you with that, in case something goes awry.
What happens if a translation messes up the build? Is there time for the translator to fix it?
Not really, but sometimes the errors are simple, like a mistyped XML tag, meaning we can fix them ourselves. (You have to use a decent PO-aware tool, like... oh, Emacs! Gosh, is there nothing it can't do?) :-)
In cases where the problem is *really* egregious, we have to disable the translation in question and notify the translator so they can fix it before GA. That rarely happens -- except when translators fail to translate the entities in docs-common, but in that case we can simply enter empty PO files and build anyway, notifying the translators of the need to take care of it in the next few weeks.
Paul
Thanks,
If you propose a time that you want to do this, I will fit in with you.
Regards,
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@gmail.com sub 2048g/B04CFA0C 2007-09-19 [expires: 2008-09-18]
-
Murray McAllister -
Paul W. Frields