release-howto.txt 5.6 KB
Newer Older
1 2 3 4 5

                        How to do a GIMP release
                      ----------------------------
                  a check-list for doing a GIMP release

6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
 ( ) Announce a string freeze on the GIMP Developer mailing list.
 
     Mention that a release is planned, what brach will be frozen, and
     how long the string freeze is going to last. Plan for a couple of
     weeks at least. No translatable strings must be touched during
     this time. An example announcement message is:
     https://mail.gnome.org/archives/gimp-developer-list/2016-October/msg00004.html

 ( ) Announce the planned release on the GNOME I18N mailing list.

     Let them know about the planned release, what branch it's based
     on, and how many changes to expect. An example message is:
     https://mail.gnome.org/archives/gnome-i18n/2016-October/msg00035.html

 ( ) Wait until the date specified in the announcements, use this time
     to get bug fixes applied which don't modify strings.
22

23
 ( ) Check that you have working ssh access to pentagon.gnome.org and
24 25
     that you are a member of the gimpadmins group. If not, ask
     Michael Natterer or Michael Schumacher for assistance.
26

27 28 29
 ( ) Check that download.gimp.org has enough space to upload the
     release and to place it into the download area. If not, make
     place or ask Michael Natterer or Michael Schumacher to do that.
30

31
 ( ) Check that you have admin access to the GIMP product on
32 33
     bugzilla.gimp.org and commit access to the gimp-web module, or
     that someone can do the changes for you.
34

35 36 37 38
 ( ) Check if NEWS, authors.xml (and the generated AUTHORS), README or
     INSTALL need to be updated, as well as any release notes on
     gimp.org. Don't forget to add any "Index of new symbols in GIMP
     2.x" to the gtk-doc generated devel-docs.
39

40
 ( ) Does the splash screen need to be changed?
41

42 43 44 45
 ( ) Bump the version number to an even micro in configure.ac and
     commit this change. It should be the version number of the
     release you are about to make. Releases always have even micro
     numbers.
46

47 48 49 50
     [ ] In configure.ac, modify gimp_micro_version accordingly.

     [ ] In configure.ac, modify gimp_interface_age accordingly.

51
 ( ) Make dist tarballs:
52

53 54
     [ ] Start with a checkout of the GIMP tree. Make sure the
         checkout is up to date, clean from uncommitted changes.
55

56 57
     [ ] Run 'git clean -x -d -f' (Warning: you will lose any files
         that are not added).
58

59 60 61 62
     [ ] Run 'git diff'. This should not generate any output, or your
         tree has local modifications.

     [ ] Run ./autogen.sh --enable-gtk-doc
63

64
     [ ] Run 'make' to do a complete build of the source tree.
65

66 67
     [ ] Run 'make distcheck'. Avoid passing make -j since that can
         cause mysterious fails.
68

69
     [ ] If changes to generated files are made by the above command
70 71
         (run 'git diff' to find out), commit+push them and repeat
         from the beginning of this sub-section.
72

73 74
     [ ] If there are problems reported by 'make distcheck', fix
         them. If you made changes in the tree to get 'make distcheck'
75 76
         running, commit+push them and repeat from the beginning of
         this sub-section.
77

78 79
     [ ] If 'make distcheck' passed and created tarballs, go to the
         next item.
80

81
 ( ) A successful run of the 'make distcheck' would create the final
82 83 84 85
     dist tarballs. It will include a ChangeLog generated from the
     'git log'. Note that we don't bother with any release commit,
     that's what tags are for (see below).

86
 ( ) Tag the release (don't forget to push the tag)
87 88
       git tag -s GIMP_2_x_y
       git push origin GIMP_2_x_y
89

90
 ( ) Bump the version number (past the tagged version) in configure.ac
91 92
     to the next odd micro and commit this change. GIT versions always
     have odd micro numbers.
93

94
 ( ) Publish dist tarballs:
95

96
     [ ] Use md5sum to create a checksum of the tarball (tar.bz2).
97

98 99 100
     [ ] Upload the tarball (tar.bz2) and the .md5 file to your home
         directory on pentagon.gnome.org.  Keep a copy of the .md5
         file around.
101

102 103
     [ ] Copy the tarball and the .md5 file to its final destination
         in the download area (/srv/ftp/pub/gimp/v2.x).
104

105 106
     [ ] Update the 0.0_LATEST-IS- file in the corresponding directory
         on the download server.
107

108 109 110 111
     [ ] Change permissions of the new files to make them writable by
       	 the 'gimpadmins' group. This will allow other members of this
       	 group to correct mistakes and to update the 0.0_LATEST-IS-
       	 file next time.
112

113
 ( ) Add the new version to the GIMP product on bugzilla.gimp.org.
114

115
 ( ) Check out or update the 'gimp-web' module, check out its testing
116 117 118 119
     branch.

     [ ] Change the file content/downloads/index.md to reference the
         new source release.
120

121
     [ ] Create a news items for the release in content/news/
122

123 124 125 126
     [ ] Commit and push the changes, the web server should then
         update itself soon (every 5 minutes). Go to
         https://testing.gimp.org to verify the changes.

127 128 129 130 131 132 133 134
 ( ) Grab a properly chilled beverage and enjoy yourself.

 ( ) Give the mirrors a reasonably long time to update, then announce
     the release on gimp.org and send a release announcement to the
     gimp-user and gimp-developer mailing lists.

     [ ] Check out the gimp-web master branch and merge or cherry-pick
         the changes you did in the testing branch.
135 136 137 138 139 140

     [ ] Push the changes, the web server should then update itself
         soon (every 15 minutes). Got to https://www.gimp.org to
         verify the changes.

     [ ] Due to the tendency of news sites to front-run release
141 142
         articles even before actual announcements appear, publish
         everything as fast as possible.