On Fri, 2008-07-11 at 01:36 +0000, Paul W. Frields wrote: > Here's my plan: > * I will continue to add content if/as needed to > https://fedoraproject.org/wiki/User:Pfrields/Drafts/ReleaseNotesHowto to > document how the current process works. > * If you come, be prepared to take on a task and doggedly pursue it to > completion by the following week. We need action. > * My general idea for the new process is to: > 1. Move each of the pieces of fedora-release-notes into git repos The first one of these is done, to start with: https://fedorahosted.org/release-notes I think we can move along with a parallel workflow for a short time, with Transifex/L10n commits to CVS. Because git has such powerful merging features, we ought to be able to capture any changes necessary into the git repo later. At some point, maybe soon depending on how people feel, we can migrate the Transifex source settings to pull from the git repo(s). > 2. Write a Makefile for each of the pieces that uses > publican{,-fedora} to build what's needed for new RPMs > 3. Update fedora-release-notes RPM in Package CVS > 4. Get other packages included in comps as appropriate -- Paul W. Frields gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://paul.frields.org/ - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-docs-list mailing list fedora-docs-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list
