Re: F11 Release Announcement
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
No one has touched the wiki page and we need to get this done. I had
writers block over the weekend so no real output from my fingers. I'd
like to have something to go over in tomorrow's Docs meeting.
If anyone would like to try their hand at it...
Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.5)
iEYEARECAAYFAkoTYI4ACgkQfQTSQL0MFMFQ/gCg0BYr59RYl6m1xGWvArY6JzE1
2fMAniiERq74trgXDRnnZFdNwm5DY+1H
=LITf
-----END PGP SIGNATURE-----
On Tue, May 19, 2009 at 16:49, Jack Aboutboul <jaa(a)redhat.com> wrote:
> Any updates on this?
>
> Jack
>
> Eric Christensen wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I have started a wiki page[1] for the F11 Release Announcement. The
>> Docs Project has started putting together some ideas but I'd like to
>> open up the opportunity for writing the announcement to the marketing
>> team as well. If you are interested in helping out, please surf on
>> over to the wiki and put your ideas down. I'd like to have this done
>> by Wednesday, May 20th.
>>
>> [1] http://fedoraproject.org/wiki/Release_Announcement_for_F11
>>
>>
>> Thanks,
>> Eric
>>
>> Docs Project
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.9 (GNU/Linux)
>> Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.5)
>>
>> iEYEARECAAYFAkoNmFgACgkQfQTSQL0MFMGdiACgn0wAaJ4wjkuFiFXQNBVVi1Ll
>> kboAniOdjFSFAQCwaFrKhpPBvZu8EoBA
>> =gNx9
>> -----END PGP SIGNATURE-----
>>
>>
>
>
15 years
Re: users-guide
by Ruediger Landmann
daniel cabrera wrote:
>
> Now, there are a few lines that we can't translate because we don't
> see the strings in the .pot file. Nothing really serious, but we
> thought that you should know this. Those lines are:
>
Thanks very much for this Daniel; Geert reported a similar problem with
the POT file for the Installation Guide. This seems to have been an
unfortunate side effect of merging the separate Publican POT files.
Since it's only a few strings, I propose that we leave this alone until
Transifex 0.6 becomes available and allows translators to access the
original Publican POT files. (I've confirmed that the strings are
present in the original POT files, but for some reason were not included
by the msgcat process...)
Is this OK with everyone?
Cheers
Ruediger
15 years
New book endorsement
by Roy Ellwood
Hi
I am new to this list
I am posting because I have just finished a new book 'Build a home webserver using Fedora Core 10'
It is a practical guide to doing 'what it says on the tin' - but, it is not just Fedora - it covers the hardware, broadband, IPCOP router, configuring apache, MailScanner, etc, etc.
I realise that it is finished just in time for Fedora Core 11 to be released - so another version will quickly follow
The book is not published yet, but I intend to use lulu.com, and using this method of publishing means that I already have a proof copy of the book, and can print more.
I want Fedora to endorse the book, and the next version, and would like to add 'published with permission of the Fedora Project' etc
How do I now go about this? I am happy to post a proof copy to anyone who can provide this endorsement. But to whom? and how do I obtain a name and address?
I now need help to finalise the publication of this book. Can somebody on this list please help?
Thanks
Roy Ellwood
15 years
release notes update
by 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
15 years
Meeting tonight
by Paul W. Frields
I can't make tonight's meeting but I'll check out the logs -- I'm
interested in hearing how the release notes work went, since I was on
vacation and missed most of the fireworks. Well, except the fireworks
I saw. Which is a separate story. :-)
Paul
15 years
Leaving docs project
by Basil Mohamed Gohar
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey everyone!
I realize this isn't much more than a drop in the bucket, given that I
haven't actually contributed anything to the project at all. However, I
am formally leaving the Docs project as I feel there's little point in
being in the group and not actually doing anything. I've actually
harbored some degree of guilt as I've been in the group all this time
and yet never actually contributed anything of substance.
The greater purpose of my leaving the group is simply one of several
steps I'm trying to take to simplify my life and keep my mind unfilled
with unfinished projects. I tend to acquire projects & things to do at
a greater rate than I can dispose of them, and this has wreaked havoc
with my mind and its ability to focus.
I will probably stay subscribed to the list, at least for a while, and
this in no way affects my love of Fedora Project itself. I just feel I
have to reorganize what I have going on so I can restore myself to
productivity.
I will remain an active promoter of Fedora & free software in general to
my various circles, so rest assured that I don't plan on going anywhere.
Thanks for everything!
- --
Basil Mohamed Gohar
abu_hurayrah(a)hidayahonline.org
http://www.basilgohar.com/blog
basilgohar on irc.freenode.net
GPG Key Fingerprint: 5AF4B362
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkoM4ToACgkQaVgOCFr0s2JP4wCdHOZjBXGx0anAzs3cxGs41Fmq
8p0AoKJ3tGcso3n5KOn+nEbNQccJXTvQ
=Bet0
-----END PGP SIGNATURE-----
15 years
release notes note
by Paul W. Frields
*** meant to send earlier today and was waylaid! ***
Hi Docs guys,
I tagged the master branch 'fedora-release-notes-11.0.0' at the
appropriate commit. If we do another release as a zero-day update,
remember that we should be updating the version to 11.0.1 to reflect a
content change. (I tagged the other "extra" modules as well, like
about-fedora-11.0.0 and so forth.)
We located a problem which may have plagued John earlier. Let me see
if I can sum it up:
The fedora-doc-utils is not inserting a version number where it's
needed at times. This interferes with the much easier tarball
creation that the "extra" modules already had available. In F10 and
before, I would just do "make release-pkg" to generate a tarball in
each repo, then copy them for the SRPM.
However, instead of generating for example a homepage-11.0.0.tar.gz
file, right now you end up with a homepage-.tar.gz file. This seems
to be caused by the XSLT stored in packagin/doc-version.xsl -- it's
not pulling out the highest revision date as expected. Shouldn't be
too hard to fix but we didn't have time to delve into it last night.
One other issue that I would recommend the Docs team look at:
* We need to branch off for F11 Any Time Now. At that point, one will
need to use the f11 branch to do any further updates, like a
zero-day update or any other midstream F11 package update.
Depending on how fast you guys want to get started with cleaning up
in advance of F12, you may want that branch sooner rather than
later.
The reason I bring this up is that after release, it's good to take a
short breather, but it's also easy to let the breather become a
vacation. (I speak from deep personal experience!) Then before you
know it, it's F12 release time and nothing's fixed. In the first
weeks after release it's going to be hard for me to do much technical
work, but after June things get better for a little while at least.
I will be happy to help out wherever I can, but I think it's up to the
Docs team to come up with a compelling plan for how we want to
approach F12, before we get more than a couple weeks into the F12
schedule. This list is an opportune venue to work out the details, so
that people will see what's being planned, have a chance to
participate, and get excited.
You guys have done a heck of a job getting so much learned, so
quickly, and contributed a lot to Fedora 11. Every single release was
a learning experience for me working on Docs, and it really made me
happy to see how far I'd come since the last release. I hope you guys
feel the same and are excited about F12 challenges.
--
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
15 years
