Adding issue and merge request templates
/cc @boklm @henry @dan @ma1 @pierov @msimonelli
Looks like this:
Merge Info
Related Issues
- tor-browser#xxxxx
- tor-browser-build#xxxxx
- etc
Backport Timeline
Immediate - patchsets for critical bug fixes or other major blocker (e.g. fixes for a 0-day exploit) OR patchsets with trivial changes which do not need testing (e.g. fixes for typos or fixes easily verified in a local developer build) Next Minor Stable Release - patchset that needs to be verified in nightly before backport Eventually - patchset that needs to be verified in alpha before backport No Backport - patchset for the next major stable Upstream Merging
Merge to base-browser
- typically for!fixups
to patches in thebase-browser
branch, though sometimes new patches as well
- NOTE: if your changeset includes patches to both
base-browser
andtor-browser
please please make separate merge requests for each partIssue Tracking
Link resolved issues with appropriate Release Prep issue for changelog generation Change Description
Edited by morgan