release notes update

[Susan Lauber]

A number of people were watching chaos last night in #fedora-docs.  It
wasn't as much chaos as it appeared at times but still...
I thought I would try to explain what was going on - at least for
Sparks since he asked :)

As I know it from last night and I am sure missing a few points....

Earlier this week jjmcd built and submitted the release candidate (rc)
version of the rpm on time per the schedule.
Problem:  it had the wrong /usr/share/doc/HTML/index.html (and
translations).  The correct xml content (and translations) was in git
- just not getting built.

A number of people (quaid, zoglesby, and mostly stickster) helped last
night to fix that problem and build a new rpm and get it to f13 for
last night's build and eventually the rc.
fedora-release-notes.11.0.0-2.fc11  should be in koji

Meanwhile there was a discussion of "as long as we are pushing a new
rpm late anyways...."  should we include a couple of other changes.

One went in:  There had been a paragraph chopped out of I18n since it
would not build correctly for any language.  It was weird because all
test builds worked fine but when done by rpm it failed miserably.
Turned out to be  single quotes that needed to be double quotes and
rudi had fixed it and pushed everything and so that one made it back
in no problem.

The other did not:  There is a paragraph replacement concerning sound.
 There is now a gui option to replace the previously mentioned command
line solution.  There was great debate about
a. do not include until zero day (the winner is option a)
b. include in english but not translated.
c. include and wait for translation (not really an option since the
rpm was needed within the hour)

Current status on changes to r-n:
1. rudi pulled the diff from the wiki for the sound issue and
committed it to master branch. 1b. but stickster reverted to make the
rpm 1c. so someone needs to revert the revert (rudi?)

2. other changes and additions from release candidate review need to
be added as available - however keep in mind that tx has only a few
hours to update this time around.
so nit pickin changes are frowned upon.

3. The schedule
[http://poelstra.fedorapeople.org/schedules/f-11/f-11-docs-tasks.html]
says convert all wiki changes to xml beginning on the 21st and new pot
on 25th.  but it also says new rpm on 25th for GA on 26th.
I think the pot needs to be late on May 22 or early May 23 so the rpm
can get in early on 25th for GA....  [ And those are probably UTC
dates which for us US folks means the evening before....]

4. When building the final rpm - there are scripts in git
[http://git.fedorahosted.org/git/docs/release-notes.git].  In the
master branch, and in the build subdir.  (laubersm notes that she
should add a readme to that dir)

Hope that helps - or at least entertains.

-Susan

-- 
Susan Lauber, (RHCX, RHCA, RHCSS)
Lauber System Solutions, Inc.
http://www.laubersolutions.com
gpg: 15AC F794 A3D9 64D1 D9CE  4C26 EFC3 11C2 BFA1 0974

[Susan Lauber]

On Thu, May 14, 2009 at 10:58 AM, Susan Lauber
<laubersm(a)fedoraproject.org&gt; wrote:
>  A number of people were watching chaos last night in #fedora-docs.
>  It
>  wasn't as much chaos as it appeared at times but still...
>  I thought I would try to explain what was going on - at least for
>  Sparks since he asked :)
>
>  As I know it from last night and I am sure missing a few points....
>
>  Earlier this week jjmcd built and submitted the release candidate (rc)
>  version of the rpm on time per the schedule.
>  Problem:  it had the wrong /usr/share/doc/HTML/index.html (and
>  translations).  The correct xml content (and translations) was in git
>  - just not getting built.
>
>  A number of people (quaid, zoglesby, and mostly stickster) helped last
>  night to fix that problem and build a new rpm and get it to f13 for
>  last night's build and eventually the rc.
>  fedora-release-notes.11.0.0-2.fc11  should be in koji
>
>  Meanwhile there was a discussion of "as long as we are pushing a new
>  rpm late anyways...."  should we include a couple of other changes.
>
>  One went in:  There had been a paragraph chopped out of I18n since it
>  would not build correctly for any language.  It was weird because all
>  test builds worked fine but when done by rpm it failed miserably.
>  Turned out to be  single quotes that needed to be double quotes and
>  rudi had fixed it and pushed everything and so that one made it back
>  in no problem.
>
>  The other did not:  There is a paragraph replacement concerning sound.
>   There is now a gui option to replace the previously mentioned command
>  line solution.  There was great debate about
>  a. do not include until zero day (the winner is option a)
>  b. include in english but not translated.
>  c. include and wait for translation (not really an option since the
>  rpm was needed within the hour)
>
>  Current status on changes to r-n:
>  1. rudi pulled the diff from the wiki for the sound issue and
>  committed it to master branch. 1b. but stickster reverted to make the
>  rpm 1c. so someone needs to revert the revert (rudi?)
>
>  2. other changes and additions from release candidate review need to
>  be added as available - however keep in mind that tx has only a few
>  hours to update this time around.
>  so nit pickin changes are frowned upon.
>
>  3. The schedule
>  [http://poelstra.fedorapeople.org/schedules/f-11/f-11-docs-tasks.html]
>  says convert all wiki changes to xml beginning on the 21st and new pot
>  on 25th.  but it also says new rpm on 25th for GA on 26th.
>  I think the pot needs to be late on May 22 or early May 23 so the rpm
>  can get in early on 25th for GA....  [ And those are probably UTC
>  dates which for us US folks means the evening before....] 
And when I finally read the last line of the schedule, the lightbulb comes on.
The zero day translation are online only - not in the rpm.  But I
guess the english does make it into the GA rpm?

I think the sound issue should get translated and into the GA rpm.
How long do we wait for "anything else" to pop up before we push that
new pot and just get it done?
trans list has been warned the one paragraph might be coming and the
general idea is that it should only take a few minutes for the one
paragraph.  There was a single +1 (no other comments) from that email
to trans list.

>  4. When building the final rpm - there are scripts in git
>  [http://git.fedorahosted.org/git/docs/release-notes.git].  In the
>  master branch, and in the build subdir.  (laubersm notes that she
>  should add a readme to that dir) 
I added a readme.build to the directory.

>  Hope that helps - or at least entertains.
>  
-- 
Susan Lauber, (RHCX, RHCA, RHCSS)
Lauber System Solutions, Inc.
http://www.laubersolutions.com
gpg: 15AC F794 A3D9 64D1 D9CE  4C26 EFC3 11C2 BFA1 0974

[Eric Christensen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, May 14, 2009 at 12:13, Susan Lauber  wrote:
>  On Thu, May 14, 2009 at 10:58 AM, Susan Lauber
>   wrote:
> > A number of people were watching chaos last night in #fedora-docs.  It
> > wasn't as much chaos as it appeared at times but still...
> > I thought I would try to explain what was going on - at least for
> > Sparks since he asked :) 
And I do appreciate it as I was on a different level of chaos last night.

>  And when I finally read the last line of the schedule, the lightbulb
> comes on.
>  The zero day translation are online only - not in the rpm.  But I
>  guess the english does make it into the GA rpm?
>
>  I think the sound issue should get translated and into the GA rpm.
>  How long do we wait for "anything else" to pop up before we push that
>  new pot and just get it done? 
I don't think we should wait that long.  If we aren't going to deal
with the small stuff I think we should get the po in front of the
translators as soon as possible.  While the Spanish translators have
said "no problem" we haven't heard anything from the other groups (not
that I see this as a big deal).  I would hate to think that this
project will become the thorn in the sides of all the translators (any
more than it already is) so I think giving more time to do the fixes
would be helpful.

Are there any other items that need to be repaired in the RNs?

Eric
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.5)
>
> iEYEARECAAYFAkoMU70ACgkQfQTSQL0MFMGXKwCfRPRcQlZvjh/ZgKlblpb348vo
> kf8AoMsjxTiFJwI346oYYATOHVrHGJas
> =JVC6
> -----END PGP SIGNATURE-----

[Paul W. Frields]

On Thu, May 14, 2009 at 01:24:14PM -0400, Eric Christensen wrote:
>  -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>  
>  On Thu, May 14, 2009 at 12:13, Susan Lauber  wrote:
>  > On Thu, May 14, 2009 at 10:58 AM, Susan Lauber
>  >  wrote:
>  >> A number of people were watching chaos last night in #fedora-docs.  It
>  >> wasn't as much chaos as it appeared at times but still...
>  >> I thought I would try to explain what was going on - at least for
>  >> Sparks since he asked :)
>  
>  And I do appreciate it as I was on a different level of chaos last night. 
Susan, you are AWESOME with a capital AWESOME.

>  > And when I finally read the last line of the schedule, the
> lightbulb comes on.
>  > The zero day translation are online only - not in the rpm.  But I
>  > guess the english does make it into the GA rpm?
>  >
>  > I think the sound issue should get translated and into the GA rpm.
>  > How long do we wait for "anything else" to pop up before we push that
>  > new pot and just get it done?
>  
>  I don't think we should wait that long.  If we aren't going to deal
>  with the small stuff I think we should get the po in front of the
>  translators as soon as possible.  While the Spanish translators have
>  said "no problem" we haven't heard anything from the other groups (not
>  that I see this as a big deal).  I would hate to think that this
>  project will become the thorn in the sides of all the translators (any
>  more than it already is) so I think giving more time to do the fixes
>  would be helpful.
>  
>  Are there any other items that need to be repaired in the RNs? 
Sorry if I'm coming in late -- emerging from a battle of the
deadlines. :-)

Now that f-r-n-11.0.0-2 is off to print, we should put any changes out
in the POT/PO for shipping to translators.  That way we can maximize
the time they have to translate for both the web publication, and a
zero-day update of the RPM package.

Is there a hole in this plan?  If not, who's going to make those changes?

-- 
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

[Ruediger Landmann]

Paul W. Frields wrote:
>  Now that f-r-n-11.0.0-2 is off to print, we should put any changes
> out
>  in the POT/PO for shipping to translators.  That way we can maximize
>  the time they have to translate for both the web publication, and a
>  zero-day update of the RPM package.
>
>  Is there a hole in this plan?  If not, who's going to make those changes?
>
>     
I'm happy to push the changes if nobody spots a hole in the plan in the 
next 24 hours... (since I've already got local copies here)

Apart from the troublesome table in i18n and the Volume Control change, 
are there any other changes anyone knows about?

Cheers
Rudi

[Susan Lauber]

On Sun, May 17, 2009 at 7:54 PM, Ruediger Landmann
<r.landmann(a)redhat.com&gt; wrote:
>  Paul W. Frields wrote:
> >
> > Now that f-r-n-11.0.0-2 is off to print, we should put any changes out
> > in the POT/PO for shipping to translators.  That way we can maximize
> > the time they have to translate for both the web publication, and a
> > zero-day update of the RPM package.
> >
> > Is there a hole in this plan?  If not, who's going to make those changes?
> >
> >
>
>  I'm happy to push the changes if nobody spots a hole in the plan in the next
>  24 hours... (since I've already got local copies here) 
Thanks Rudi!!!

>  Apart from the troublesome table in i18n and the Volume Control change, are
>  there any other changes anyone knows about? 
I did a quick scan of my starred emails...
1. Something about archer
https://fedoraproject.org/wiki/Features/Archer#Release_Notes but John
replied he has added that one.
2. Something about moin that should have made it well before the last
cutoff but no one answered the email so it may be worth checking...
https://www.redhat.com/archives/fedora-docs-list/2009-April/msg00123.html
3.  Is there anything on presto? - which has gone back and forth on
availability but I think ended up included. I'll be honest, I have not
looked.   https://fedoraproject.org/wiki/Features/Presto#Release_Notes

-Susan

-- 
Susan Lauber, (RHCX, RHCA, RHCSS)
Lauber System Solutions, Inc.
http://www.laubersolutions.com
gpg: 15AC F794 A3D9 64D1 D9CE  4C26 EFC3 11C2 BFA1 0974

[Ville-Pekka Vainio]

su, 2009-05-17 kello 22:11 -0400, Susan Lauber kirjoitti:
>  2. Something about moin that should have made it well before the
> last
>  cutoff but no one answered the email so it may be worth checking...
>  https://www.redhat.com/archives/fedora-docs-list/2009-April/msg00123.html 
I haven't been following the Release Notes process closely, so I'm not
sure whether what's on the wiki matches what is or will be in the
release-notes rpm, but someone has added the moin bit here:
https://fedoraproject.org/wiki/Docs/Beats/WebServers - thanks. There is
a small typo in there, though. '/user/share/doc/moin-1.8.2/*' should be 
'/usr/share/doc/moin-1.8.2/*', but I don't consider that to be serious,
since I think server admins will most likely know what was meant and
where the files really are.


-- 
Ville-Pekka Vainio

[Paul W. Frields]

On Sun, May 17, 2009 at 10:11:49PM -0400, Susan Lauber wrote:
>  I did a quick scan of my starred emails...
>  1. Something about archer
>  https://fedoraproject.org/wiki/Features/Archer#Release_Notes but John
>  replied he has added that one.
>  2. Something about moin that should have made it well before the last
>  cutoff but no one answered the email so it may be worth checking...
>  https://www.redhat.com/archives/fedora-docs-list/2009-April/msg00123.html
>  3.  Is there anything on presto? - which has gone back and forth on
>  availability but I think ended up included. I'll be honest, I have not
>  looked.   https://fedoraproject.org/wiki/Features/Presto#Release_Notes 
The DeltaRPMs will be available, but users do indeed need to install
yum-presto.  That's what the Presto feature release note says.

I don't see this in our Release Notes anywhere, but if we're making
other changes, this will be a biggie.  I'd suggest that it go in the
Overview section, and if more detail is desired, a link to the feature
page.

-- 
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

[Ruediger Landmann]

OK - I just pushed the following changes (and incremented the version 
number to 1.4):

* Fixed the table problem in i18n
* Updated the Volume Control information (including the correct GNOME 
menu entry -- thanks, Paul!)
* Added a note about Archer (including the warning that Tom Tromey 
requested) This actually hadn't been included...
* Added a note about moin
* Added a note about Presto
* Added a link to a wiki page about configuring fingerprint readers 
(Thanks Domingo)

Thanks, Susan for your excellent roadmap of what was missed first time 
around, and a BIG thanks in advance to the translators for your 
willingness to get a 0-day update ready!

Cheers
Ruediger

[Ruediger Landmann]

I just discovered that the merged version of the .pot files that I 
checked in earlier today (po/release-notes.pot) was broken. I've fixed 
it and checked it in again, but it means that Transifex is showing some 
very strange statistics at the moment. This should be fixed the next 
time Transifex refreshes (in a few hours).

Sorry!
Ruediger

[John J. McDonough]

----- Original Message ----- 
From: "Paul W. Frields" <stickster(a)gmail.com&gt;
To: <fedora-docs-list(a)redhat.com&gt;
Sent: Friday, May 15, 2009 4:23 PM
Subject: Re: release notes update


>  Susan, you are AWESOME with a capital AWESOME.
>  
And let me second that, with a double underline.

Just got back from Dayton, not even completely unpacked, but it is good to 
see the Docs Team stood up, as I knew they would.  And seeing Susan's 
leadership in this is superb, but to me, not really a surprise.

--McD