Changes between Version 6 and Version 7 of SubmittingPatches
- Timestamp:
- Oct 5, 2011, 1:35:23 AM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SubmittingPatches
v6 v7 7 7 * Make sure you've updated to the latest version of the code (and merged in your own changes). 8 8 * Create a patch, with `svn diff` (or the equivalent "create patch" feature in TortoiseSVN). 9 * Attach it to a Trac ticket (an existing ticket if there's a relevant one, else a new one), and add "review" to the keywordslist. (The keyword makes it show up on [query:status=new|assigned|reopened&keywords=~review this query].)9 * Attach it to a Trac ticket (an existing ticket if there's a relevant one, else a new one), prefix the ticket '''Summary''' with "[PATCH]", set the ticket '''Milestone''' to the current release, and add "review" to the '''Keywords''' list. (The keyword makes it show up on [query:status=new|assigned|reopened&keywords=~review this query].) 10 10 * One of the core developers should then review it and maybe suggest some changes. 11 11 * When it's considered okay, they should commit it to SVN. 12 12 * If you don't hear anything within a reasonable time period (maybe a week or two), feel free to post a reminder on the [http://www.wildfiregames.com/forum/index.php?showforum=312 forum]. 13 13 14 The person submitting the patch must agree that it is their own work (or else make it clear where it came from) , and agree to licensing the work as BSD or GPL (we're not yet quite sure which we want...)14 The person submitting the patch must agree that it is their own work (or else make it clear where it came from) and agree to licensing the work as GPL.