🌍
English
Differences
This shows you the differences between two versions of the page.
|
dev:core:subversion [2011/09/13 13:30] 127.0.0.1 external edit |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Subversion (SVN) ====== | ||
| - | |||
| - | ==== Write access ==== | ||
| - | |||
| - | How to have write access to Subversion repository? | ||
| - | |||
| - | * ask it with the [[http://piwigo.org/contact|contact form]] | ||
| - | * if project administrators agree with your request, we will ask you to provide a "htpasswd string" that can be generated on [[http://aspirine.org/htpasswd_en.html|this page]] (select the MD5 algorithm) | ||
| - | * configure tools (Linux, [[en:svn+ssh+win32|Windows XP]]) | ||
| - | |||
| - | You'll find documentation on internet. External links: | ||
| - | * [[http://subversion.tigris.org|Subversion official website]] | ||
| - | |||
| - | ==== First steps with Subversion ==== | ||
| - | |||
| - | Before going any further, take a look at [[dev:about:release_and_branchs|Branch and releases]] to understand what we mean when talking about trunk, branches and releases. | ||
| - | |||
| - | <code bash># working on trunk | ||
| - | $ svn checkout http://piwigo.org/svn/trunk | ||
| - | $ cd trunk | ||
| - | $ vi feed.php | ||
| - | $ vi notification.php | ||
| - | $ svn diff feed.php notification.php | ||
| - | $ svn commit -m "add new informations in RSS notification feed" feed.php notification.php | ||
| - | |||
| - | # working on branch 1.5 | ||
| - | $ svn checkout http://piwigo.org/svn/branches/1.5 | ||
| - | $ cd 1.5 | ||
| - | $ vi include/functions_html.inc.php | ||
| - | $ svn commit -m "bug 256 fixed: wrong tags for HTML menus" include/functions_html.inc.php</code> | ||
| - | |||
| - | ==== Commit logs ==== | ||
| - | |||
| - | * must be written in english | ||
| - | * each line should not exceed 80 columns | ||
| - | |||
| - | Each commit log have a distinct paragraph for each modification done. Two paragraphs are separaterd with an empty line. Each kind of modification must be easy to understand just by reading the log. | ||
| - | |||
| - | The following example shows a commit log with several kind of modification. Of course, you wont ever have as many modification in a single commit, it's just an example. Thanks to be rigorous enough for "bug XXX fixed:", "merge -r?:? from ? into ? (bug ? fixed)", "feature XXX added:". | ||
| - | |||
| - | <code>bug 205 fixed: advise to perform maintenance actions at the end of upgrade | ||
| - | process.</code> | ||
| - | |||
| - | <code>feature 147 added: add a menu to manage manually create_listing_file.php | ||
| - | on remote sites</code> | ||
| - | |||
| - | <code>new: "quick start" section in Administration>General>Instructions | ||
| - | |||
| - | improvement: long localized messages are in HTML files instead of $lang | ||
| - | array. This is the case of admin/help and about pages.</code> | ||
| - | |||
| - | <code>deletion: of unused functions (ts_to_mysqldt, is_image, TN_exists, | ||
| - | check_date_format, date_convert, get_category_directories, | ||
| - | get_used_metadata_list, array_remove, pwg_write_debug, | ||
| - | get_group_restrictions, get_all_group_restrictions, is_group_allowed, | ||
| - | style_select, deprecated_getAttribute).</code> | ||
| - | |||
| - | When a commit is a merge from a branch to another, give details about the merge and what was merge (copy log from original commit). | ||
| - | |||
| - | <code>merge -c2811 from branch 2.0 to trunk | ||
| - | |||
| - | based on forum discussion, a comment is added to explain why c13y_upgrade | ||
| - | plugin is activated at this precise moment.</code> | ||