├── .gitignore
└── ReleaseChecklist


/.gitignore:
--------------------------------------------------------------------------------
1 | .gitignore
2 | dist
3 | tmp
4 | 


--------------------------------------------------------------------------------
/ReleaseChecklist:
--------------------------------------------------------------------------------
 1 | Release Checklist
 2 | -----------------
 3 | 
 4 | All the instructions below refer to the version of the code in the
 5 | appropriate release branch.  The expectation is that the master branch
 6 | is where main development happens and that we'll have a branch for
 7 | each individual major release version:
 8 | 
 9 |  >--+----------------+--------------------------> master
10 |     |                \----*----------> 3.1.x
11 |     |                     3.1
12 |     \----*----------*------------*-------> 3.0.x
13 |          3.0        3.0.1        3.0.2
14 | 
15 | The git based instructions below all refer to operations in the
16 | RELEASE BRANCH.
17 | 
18 | 1) Notify gallery-redistributors list of upcoming release
19 | 
20 | 2) Make sure all unit tests pass.  You can check Travis:
21 |    https://travis-ci.org/gallery/gallery3/branches
22 | 
23 | 3) Update the gallery3 VERSION constant in gallery3/modules/gallery/helpers/gallery.php
24 |    if necessary.  Typically, this version should be updated long before release so
25 |    that users can track which version they're using.
26 | 
27 | 4) Look over gallery3/README and touch up anything version specific
28 | 
29 | 5) Tag the release, eg:
30 |    $ git tag 3.0.2
31 |    $ git push --tags
32 | 
33 | 6) Build the release, eg:
34 |    php build.php 3.0.2
35 | 
36 | 7) Upload file to SF.net
37 | 
38 | 8) Create a forum topic for the release, leave it unpublished.
39 | 
40 | 9) One final pass over the GMC news story, make sure the download link is correct.
41 | 
42 | 10) Click "publish" on the GMC story and the forum topic
43 | 
44 | 11) Update http://galleryproject.org/admin/build/block/configure/block/1
45 | 
46 | 12) Update the release date on the Codex on http://codex.galleryproject.org/Downloads and
47 |     http://codex.galleryproject.org/Main_Page
48 | 
49 | 13) Update the 3 release_xxx fields on http://galleryproject.org/admin/gmc_versioncheck --
50 |     all the rest should be fine.  The branch entries are updated automatically.
51 | 
52 | 14) Close the old milestone, create a milestone for the next release,
53 |     create a version for the milestone just closed and make it the
54 |     default, make the new milestone the default.
55 | 
56 | 15) Update the topic on IRC
57 | 
58 | 16) Update sf.net, opensourcecms.com stories with the first paragraph of the
59 |     news announcement from galleryproject.org and URLs to the news story and the file.
60 |     
61 |     * https://sourceforge.net/news/submit.php?group_id=7130
62 |     * http://members.opensourcecms.com/edit/
63 | 
64 | 17) E-mail gallery-announce and gallery-redistributors announcing the
65 |     release, linking to the GMC story and download URL
66 | 
67 | 


--------------------------------------------------------------------------------