Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
staging [2009/11/22 20:25] mdc |
staging [2010/01/15 13:00] (current) stefanha |
||
---|---|---|---|
Line 173: | Line 173: | ||
=== Indicating readiness for final merge review === | === Indicating readiness for final merge review === | ||
- | When a sponsor believes that an appropriate window of opportunity for review has expired, they may then rename their branch in the staging repository in the following format: | + | When a sponsor believes that an appropriate window of opportunity for review has expired, they may send a pull request email to staging@etherboot.org. This is an indication to main branch maintainers that the feature is now ready for final merge review. |
- | sponsor_name-task_number-feature_branch_name-ready | + | The email subject should be as follows: |
- | This is an indication to main branch maintainers that the feature is now ready for final merge review. | + | [PULL REQUEST] sponsor_name-task_number-feature_branch_name |
+ | |||
+ | The pull request email message can be generated as follows: | ||
+ | |||
+ | $ # Currently on the staging branch | ||
+ | $ git request-pull master git://git.etherboot.org/scm/gpxe-staging.git | ||
Note to staging tree maintainers: | Note to staging tree maintainers: | ||
Line 185: | Line 190: | ||
$ git push staging local_name:refs/heads/remote_name | $ git push staging local_name:refs/heads/remote_name | ||
- | Main repository maintainers can easily check for branches pending final merge review with | + | Main repository maintainers respond to the pull request email by performing final review and merging the branch if it passes review. |
- | + | ||
- | $ git branch -r -v | grep ready | + | |
- | + | ||
- | or by using gitweb to view all branches in the staging repository: | + | |
- | + | ||
- | http://git.etherboot.org/?p=gpxe-staging.git;a=heads | + | |
=== Final merge review procedure === | === Final merge review procedure === |