10
10
If you're helping the Release Manager (RM) for one reason or another, you
11
11
may notice that he didn't follow that document scrupulously. He may have
12
good reasons to do that, I may also have missed some parts.
12
good reasons to do that but he may also have missed some parts.
14
14
Follow the document yourself and don't hesitate to create the missing
15
15
milestones for example (we tend to forget these ones a lot).
307
307
Releases until the final one
308
308
----------------------------
310
Congratulations, you made it. Have a beer or a fruit juice, it's on the
311
house and don't force you to drink alcohol.
313
You have made your first release, that's great. If it was a beta, or
314
candidate, you're not finished, another beta or candidate or hopefully a
315
final release is still to come.
317
The process is the same as for the first release, go to `Starting the
318
release phase`_ and follow the instructions again. Some details changed
310
Congratulations - you have made your first release. Have a beer
311
or fruit juice - it's on the house! If it was a beta, or
312
candidate, you're not finished yet. Another beta or candidate or
313
hopefully a final release is still to come.
315
The process is the same as for the first release. Goto `Starting the
316
release phase`_ and follow the instructions again. Some details change
319
317
between beta, candidate and final releases, but they should be
320
documented. If they aren't clear enough to your taste, fix them.
318
documented. If the instructions aren't clear enough, please fix them.
added
removed
doc/developers/releasing.txt
