Submitting code in response to a release version initiation

Submitting code in response to a release version initiation

 

Code submitted in response to a release version initiation should consist of a single push consisting of a change to the upper level OSEHRA Code Base ATTESTATION file. The change should consist of the addition of a single line as the topmost attestation.  The line will contain the SHA1 key for the repository to be released, the date, and the name of the attester. Figure 1 shows an example ATTESTATION file after the addition of the first release attestation.  Again complete the “Primary Developer Checklist” and attach it to the Jira ticket prior to performing the push to Gerrit; although, for this specific case, most of the entries will be N/A.  For the short description, the message should replicate the Jira title “Initiation of release #(SHA1)”.  The long description can contain release notes along with the reference to the correct Jira ticket.

Figure 1- Structure of the ATTESTATION file.  The highlighted line shows the structure of the new addition containing the SHA1 key, date and attester name.

 

Return to Previous Page

Return to the Main Page

 

like0

Contributors