User Tools

Site Tools


wiki:development:release-howto

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
wiki:development:release-howto [2022/08/29 23:23]
ionic Update instructions with information previously not explicitly provided, like copyright date updates and bug cleaning.
wiki:development:release-howto [2022/08/29 23:29]
ionic Add disclaimer that is not a complete list.
Line 4: Line 4:
  
 The prerequisite for these steps is to login to japsand as ''x2go-admin''. The prerequisite for these steps is to login to japsand as ''x2go-admin''.
 +
 +This list is not complete. It's meant as a general checklist. Some packages require additional steps not mentioned here, but these are common ones that should fit most components.
  
 ^ Variable ^ Meaning ^ ^ Variable ^ Meaning ^
Line 23: Line 25:
 |  10  | Remove bug spam for all bug reports closed in this release | This process is complicated and must be done on **ymir** (packages.x2go.org) as the **debbugs** user, which requires root access. This is ''not'' all required information. | |  10  | Remove bug spam for all bug reports closed in this release | This process is complicated and must be done on **ymir** (packages.x2go.org) as the **debbugs** user, which requires root access. This is ''not'' all required information. |
 | ::: | <code>cd /var/lib/debbugs/spool/db-h</code> | Switch to the database directory. | | ::: | <code>cd /var/lib/debbugs/spool/db-h</code> | Switch to the database directory. |
-| ::: | <code>cp -av XX/bugnumberXX.log{,.bak} | Create backup of original log. The log file contains all messages that have been sent and received during the bug's life cycle, including status changes. |+| ::: | <code>cp -av XX/bugnumberXX.log{,.bak}</code> | Create backup of original log. The log file contains all messages that have been sent and received during the bug's life cycle, including status changes. |
 | ::: | ::: | The directory containing the bug report log is always named after the last two digits (0-padded, if necessary) of the bug report number. | | ::: | ::: | The directory containing the bug report log is always named after the last two digits (0-padded, if necessary) of the bug report number. |
 |  11  | <code>/usr/lib/debbugs/cleanbug bugnumber</code> | This tool will interactively list all messages (including status changes) in the report and asks whether to keep or discard them. | |  11  | <code>/usr/lib/debbugs/cleanbug bugnumber</code> | This tool will interactively list all messages (including status changes) in the report and asks whether to keep or discard them. |
wiki/development/release-howto.txt ยท Last modified: 2022/08/29 23:29 by ionic