operations/docs
operations/docs
3
1
Fork 9
Code Issues 4 Pull requests Activity Actions

Update to reflect the move away from CVS

Browse source
This commit is contained in:
Ben Cotton 2021-05-26 14:54:48 -04:00
commit c211dfc727
1 changed files with 15 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

32
modules/ROOT/pages/pgm_guide/schedule.adoc
View file

@ -35,7 +35,7 @@ The Preferred Final target date is the “master milestone” against which ever
TIP: Before publishing the schedule, check to be sure that it doesn't conflict too horribly with major holidays, etc.
To publish the schedule, *Export to Microsoft Project (XML)* and save the file to the CVS `f-N` directory as `Fedora.Schedule.xml`.
To publish the schedule, *Export to Microsoft Project (XML)* and save the file to the `f-N` directory in the https://pagure.io/fedora-pgm/schedule[schedule repository] as `Fedora.Schedule.xml`.
TIP: If *Export to Microsoft Project (XML)* is not an option, you might need to switch to Gantt view.
Smartsheet isn't very smart in that regard.
@ -45,23 +45,20 @@ When schedules slip:
1. Add a new target date (e.g. Beta target date #2)
2. Update the “Current X target date” when you know it's really going to happen
== CVS repo
== Git repo
Red Hat product schedules are kept in a CVS repository.
See the https://docs.engineering.redhat.com/display/EPM/CVS+schedule+storage+local+setup[internal documentation] for instructions on setting up your machine.
Check out the repo and go to `program/fedora`, which has schedules back through Fedora Core 5.
The files used to publish the scripts live in a https://pagure.io/fedora-pgm/schedule[git repository].
To create a schedule for a new version:
To create a schedule for a new version (f-30 in this example):
1. `mkdir f-30`
2. `cvs add f-30`
3. `vi Makefile` # copy forward from previous and change the version
4. Export the XML file (see previous section)
5. `cvs add Fedora.Schedule.xml Makefile`
6. `cvs ci -m ‘Your commit message here’`
2. `cp ../f-29/Makefile . && vi Makefile` # copy forward from previous and change the version
3. Export the XML file (see previous section)
4. `git add Fedora.Schedule.xml Makefile`
6. `git commit -m ‘Your commit message here’`
7. to see the changes locally: `make` (`make clean` cleans up your mess)
8. # fedora/common/Makefile.common has settings for rsyncing
9. `make publish` #publish html and friends to fedorapeople
10. Product Pages automatically picks up when you check in to CVS
8. `make publish` #publish html and friends to fedorapeople
NOTE:: The rsync invocations in the Makefile assume you have your user name set in `~/.ssh/config` if your local name does not match your Fedora account.
== Product Pages
@ -75,12 +72,13 @@ To register a new verison in product pages:
4. Select all the sections to copy
5. Click *OK*
7. Click *Schedules* tab
8. Click *Add schedules* butotn
9. Handle: <find the file in the browser>
8. Click *Add schedules* button
9. Handle: <get the Smartsheet file URL or ID>
10. Switch draft to approved
11. Set phase to planning
TIP: Use the xml file instead of directly using Smartsheet so you get version history.
TIP: Prior to May 2021, we used a Red Hat CVS server for the schedule files.
They now are pulled directly into Product Pages from Smartsheet.
Key fields: