Changes between Version 6 and Version 7 of Howto

Sep 13, 2009, 6:48:18 PM (6 years ago)



  • Howto

    v6 v7  
    5050= Create a Patch = 
     51For open source projects (like this one) everyone has read access to the repository, and anyone can make a contribution to the project. So how are those contributions controlled? If just anyone could commit changes, the project would be permanently unstable and probably permanently broken. In this situation the change is managed by submitting a patch file to the development team, who do have write access. They can review the patch first, and then either submit it to the repository or reject it back to the author.  
     52Patch files are simply Unified-Diff files showing the differences between your working copy and the base revision.  
    52 For now see the [wiki:Development] page 
     54Prepare your changes according to the guide lines on the [wiki:Development] page 
     56Once your changes are ready you can prepare them for deployment using the following steps: 
     571) create a patch file 
     582) attach the patch file to the relevant ticket 
     62''Creating a patch file''[[BR]] 
     64First you need to make and test your changes. Then instead of using TortoiseSVN → Commit... on the parent folder, you select TortoiseSVN → Create Patch... [[BR]] 
     66you can now select the files you want included in the patch, just as you would with a full commit. This will produce a single file containing a summary of all the changes you have made to the selected files since the last update from the repository. [[BR]] 
     68You can produce separate patches containing changes to different sets of files. Of course, if you create a patch file, make some more changes to the same files and then create another patch, the second patch file will include both sets of changes.[[BR]] 
     70Just save the file using a filename of your choice. Patch files can have any extension you like, in our project you should use the .patch extension.  The file name should look like <my_patch_file_name.patch>.  You are now ready to submit your patch file.[[BR]] 
     72You can also save the patch to the clipboard instead of to a file. You might want to do this so that you can paste it into “past bin” for review by others. Or if you have two working copies on one machine and you want to transfer changes from one to the other, a patch on the clipboard is a convenient way of doing this.[[BR]] 
     76''Submitting the patch file''[[BR]] 
     78Submitting a patch in the padre project simply means attaching the patch file created to a Ticket.[[BR]] 
     80Find the relevant ticket in Trac and attach the patch file you created to that Ticket.  If you fixed something which did not have an open ticket    you should first open a ticket and then attach the patch file.[[BR]] 
     82The patch file will be reviewed by an authorized developer who will either apply the patch or get in touch (usually on IRC with the person submitting the fix to discuss any issues[[BR]] 
    5485= Translate Padre =