Difference between revisions of "User:Dennisvd@nikhef.nl/SoftwareOverview"
From PDP/Grid Wiki
Jump to navigationJump to search| Line 5: | Line 5: | ||
{| class="wikitable" | {| class="wikitable" | ||
| | | | ||
| − | ! | + | ! resources |
| − | ! | + | ! procedures |
|- | |- | ||
! scope="row"| Source | ! scope="row"| Source | ||
| Line 14: | Line 14: | ||
* The software packages follow the GNU coding guidelines, and use automake/autoconf. | * The software packages follow the GNU coding guidelines, and use automake/autoconf. | ||
| | | | ||
| − | * Before tagging, go through [[SAC_software_procedures#Mandatory_Check_list|the mandatory checklist]]. | + | * Before tagging, go through [[SAC_software_procedures#Mandatory_Check_list|the mandatory checklist]]: |
| + | ** Update configure.ac with the right version | ||
| + | ** make distcheck | ||
| + | ** Update the files BUGS, INSTALL, NEWS, README | ||
| + | ** <tt>svn update ; svn log -v > ChangeLog</tt> | ||
| + | ** commit to SVN | ||
* Prior to preparing a release, the software should be [[SAC_software_procedures#Creating_a_tag_in_Grid_Security_Middleware|tagged]]. | * Prior to preparing a release, the software should be [[SAC_software_procedures#Creating_a_tag_in_Grid_Security_Middleware|tagged]]. | ||
|- | |- | ||
! scope="row"| Release | ! scope="row"| Release | ||
| − | | | + | | |
| − | + | When the software is ready to be released it is rolled into a source distribution tarball. The 'make dist' target makes sure this | |
| + | is a clean tarball without any files that are strictly for development and not for distribution. | ||
| + | * Run bootstrap on fc17.testbed, to use the newest possible automake/autoconf | ||
| + | * Run 'make dist' on mwsecbuild.testbed; this machine has all the required dependencies | ||
| + | | | ||
| + | * [[SAC_software_procedures#Release_software_as_tarball|make a tarball]] | ||
| + | * record the sha1 and sha256 checksums | ||
| + | * upload to software.nihkef.nl | ||
| + | * write a signed e-mail to grid-mw-security with the name of the tarball and the checksums | ||
|- | |- | ||
! scope="row"| Packaging | ! scope="row"| Packaging | ||
| Line 37: | Line 50: | ||
* EMI, IGE, UMD and other middleware integrators | * EMI, IGE, UMD and other middleware integrators | ||
* Fedora, EPEL, Debian, Ubuntu | * Fedora, EPEL, Debian, Ubuntu | ||
| − | | koji tags, sigul, mash, signed repositories, dput | + | | |
| + | koji tags, sigul, mash, signed repositories, dput | ||
| + | * write Release notes and announce on [https://mailman.nikhef.nl/mailman/listinfo/grid-mw-security-announce the announce mailing list]. | ||
| + | |||
|} | |} | ||
Revision as of 22:48, 17 January 2013
Cheat Sheet
The following table gives an overview of the workflow and procedures involving development and delivery of our software.
| resources | procedures | |||||
|---|---|---|---|---|---|---|
| Source |
|
| ||||
| Release |
When the software is ready to be released it is rolled into a source distribution tarball. The 'make dist' target makes sure this is a clean tarball without any files that are strictly for development and not for distribution.
|
| ||||
| Packaging |
|
|||||
| Distribution |
|
koji tags, sigul, mash, signed repositories, dput
|
