Difference between revisions of "Post Release Checklist"
From Apache OpenOffice Wiki
Line 19: | Line 19: | ||
<tr> | <tr> | ||
− | <td>splashscreen, about bitmap</td> | + | <td>splashscreen, about bitmap in svx/res</td> |
− | <td>update the version numbers in graphics </td> | + | <td>update the version numbers in graphics. See also i73786 to remove version info from bitmaps.</td> |
− | <td>STS/PB</td> | + | <td>STS/IS/PB</td> |
</tr> | </tr> | ||
Line 40: | Line 40: | ||
<td>Generate new alias for the update URL</td> | <td>Generate new alias for the update URL</td> | ||
<td>OF</td> | <td>OF</td> | ||
+ | </tr> | ||
+ | |||
+ | <tr> | ||
+ | <td>Readme files</td> | ||
+ | <td>Readme files contain hard coded version numbers. This numbers have to be adapted. The preferred way is to use the variable ${PRODUCTVERSION}, which is replaced during packaging process with the value from openoffice.lst.</td> | ||
+ | <td>MH</td> | ||
</tr> | </tr> | ||
Revision as of 10:29, 8 June 2007
This page contains information about what has to be done in particular modules after a release of OOo.
Module | What has to be done | Owner |
---|---|---|
offapi | Commit the types.rdb which is used in the last release. That is, exchange offapi/type_reference/types.rdb with the released types.rdb and insert a comment into offapi/type_reference/typelibrary_history.txt. Commit both. | JSC |
cli_ure | Adjust the versions of the .NET assemblies. For detailed instructions read cli_ure/readme.txt | JL |
splashscreen, about bitmap in svx/res | update the version numbers in graphics. See also i73786 to remove version info from bitmaps. | STS/IS/PB |
instsetoo_native, openoffice.lst | update the version numbers in the variables PRODUCTVERSION, ABOUTBOXPRODUCTVERSION, UPDATEURL, PACKAGEVERSION, LIBRARYVERSION | IS |
sysui, productversion.mk | update the version numbers in the variables PRODUCTVERSION, PKGVERSION, LONGPRODUCTNAME, UNIXFILENAME | IS/OBR/IHI |
Alias for UpdateURL | Generate new alias for the update URL | OF |
Readme files | Readme files contain hard coded version numbers. This numbers have to be adapted. The preferred way is to use the variable ${PRODUCTVERSION}, which is replaced during packaging process with the value from openoffice.lst. | MH |
Done after 2.0.3 release