From 4651f319a19164ee1d4fe9a15634bb378e54aeee Mon Sep 17 00:00:00 2001 From: Graeme Geldenhuys Date: Thu, 12 Feb 2015 10:10:01 +0000 Subject: Docs on what to do for a new release This is still work in progress. --- docs/release_process.txt | 45 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+) create mode 100644 docs/release_process.txt (limited to 'docs/release_process.txt') diff --git a/docs/release_process.txt b/docs/release_process.txt new file mode 100644 index 00000000..cc02bdcf --- /dev/null +++ b/docs/release_process.txt @@ -0,0 +1,45 @@ +Release process +=============== + +1. Create new release branch off 'develop': + git checkout -b release-1.x develop + +2. Bump version numbers + + docview/src/docview.rc + src/VERSION_FILE.inc + fpgui_toolkit.lpk (both X11 & gdi) + docs/manifest.xml + +3. Run localization script to update all *.po files + +4. Switch to 'develop' branch + +5. Bump version numbers - same files as step 2. + +6. Push both release and develop branches + +7. Build new documentation + [ ] INF + [ ] HTML for website + +8. Build new DocView + +9. Archive Docview and INF and release to SourceForge (Github?) + +10. Archive HTML and release to SourceForge. + +11. Push HTML API docs to website + + + +Release notification +==================== + +1. Update website with new release and changelog + +2. Post message to FPC Users mailing list + +3. Post message to Lazarus mailing list + +4. Post message to Lazarus Forum (3rd party) -- cgit v1.2.3-70-g09d2