| 4626 |
dpurdie |
1 |
Notes on this implementation of the release Note Generation Tool
|
|
|
2 |
----------------------------------------------------------------
|
|
|
3 |
|
|
|
4 |
It is intended to completely replace the existing tool and method.
|
|
|
5 |
It is intended as an iterum solution. It address several short
|
|
|
6 |
coming of the existing scheme, but is not the best final solution.
|
|
|
7 |
|
|
|
8 |
This tool does not use the RM web server in the Release Note
|
|
|
9 |
Generation Process.
|
|
|
10 |
|
|
|
11 |
The tool is designed to be run as a Cron Job - every minute.
|
|
|
12 |
|
|
|
13 |
It requires write-access to the RM database.
|
|
|
14 |
|
|
|
15 |
It is designed to run on the same machine as dpkg_archive. It may also work in close proximity.
|
|
|
16 |
|
|
|
17 |
It is the final part of the release process for a package. It will:
|
|
|
18 |
Generate the Release Note
|
|
|
19 |
Mark the package as read-only
|
|
|
20 |
Trigger transfer to remote sites via BLAT
|
|
|
21 |
Email interested users
|
|
|
22 |
|
|
|
23 |
Key features of this implementation inclued:
|
|
|
24 |
* Does not generate file checksums. The package builder does this
|
|
|
25 |
This significantly reduces network load and generation time: both problems
|
|
|
26 |
in the previous system
|
|
|
27 |
|
|
|
28 |
* Generates and mainatins an XML structure of the Release Note Data
|
|
|
29 |
|
|
|
30 |
Installation:
|
|
|
31 |
|
|
|
32 |
Can be run directly from dpkg_archive
|
|
|
33 |
|
|
|
34 |
Configute cron to run /home/buildadm/cron/generateReleaseNotes
|
|
|
35 |
|
|
|
36 |
/home/buildadm/cron/generateReleaseNotes should:
|
|
|
37 |
Setup Jats
|
|
|
38 |
Run process_release_notes.pl from dpkg_archive
|
|
|
39 |
|
|
|
40 |
|
|
|
41 |
|