Changes

Jump to navigation Jump to search
added screenshot
Line 50: Line 50:  
The final step in ensuring that the translations are merged back into the master source tree of the software is to "Commit" them. Committing is a pretty straightforward process, but you should ideally do it only after you have done the relevant checks and reviews. We recommend that you follow a 'release early and release often policy'<ref>http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html</ref> while committing, as that would get the maximum amount of exposure and testing for your translations.
 
The final step in ensuring that the translations are merged back into the master source tree of the software is to "Commit" them. Committing is a pretty straightforward process, but you should ideally do it only after you have done the relevant checks and reviews. We recommend that you follow a 'release early and release often policy'<ref>http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html</ref> while committing, as that would get the maximum amount of exposure and testing for your translations.
   −
To Commit, click on the "Commit to VCS" link that appears below each file in the "Translate" or "Review" pages.
+
To Commit, click on the "Commit to VCS" link that appears below each file in the "Translate" or "Review" pages:
 +
 
 +
[[Image:Translate-review-commit.png]]
    
..and you are done. If you don't see this link, it means "can commit to version control" permission is off. The link may also disappear if the contact with project repository is broken. Send a request to mailing list to fix this.
 
..and you are done. If you don't see this link, it means "can commit to version control" permission is off. The link may also disappear if the contact with project repository is broken. Send a request to mailing list to fix this.
21

edits

Navigation menu