Basically - I wanted to know where to start contributing changes intended for the F13 version on guides. And where to point new contributors as well.
In the meeting tonight, a discussion started about branching philosophies.
#action laubersm Bring branching topic to docs list to decide how we want to do this going forward, and record it for posterity.
I have looked at a couple of guides in git. They seem to have a master, F11, F10, etc, and various F??-tx branches.
I think we generally agree that the F??-tx branches are for the translation teams.
The rest seems to indicate a need for a F12 branch and then master becomes F13.
But when should the F12 branch appear so that work on F13 can begin?
I did not look at all the guides - there may be other schemes in use already.
So I see 2 major parts to the question:
1. Is this the branching scheme that works best for Fedora Docs group and guides?
What are the alternatives?
pros/cons? etc
2. WHEN do we branch?
Should the F12 branch been made at release of F12 so that master moves to the next version right away?
If so, how do we handle mid release updates to a guide?
Should master stay the current version until the next release alpha? Which is about now.
Or even longer?
Let the debate begin (be nice folks).
-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
-- docs mailing list docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/docs
