summaryrefslogblamecommitdiffstats
path: root/doc/RELEASING
blob: de6a09150219410612c63703c502c956b55d8a43 (plain) (tree)
1
2
3
4
5
6
7
8
9
10
11





                                    




                                                                         



                                                                  

                                                                     







                                                 
                                       









                                       
                                                                     

                
RELEASING QUILT
===============

Step 1: set the new version and test
------------------------------------

- If you can update one translation file, do so and commit the po file.
  Even better, ping the translators (their names and emails are in the po
  file headers, asking on the quilt-dev list can work too), and give them
  the opportunity to update their work. Count one week for that.
- Bump the version in AC_INIT in configure.ac.
- Regenerate configure:
  $ autoconf
  Make sure you don't use a version of autoconf older than the one
  previously used.
- Mention the new version in NEWS, with a summary of all user-visible
  changes.
- Make sure that everything builds and runs fine:
  $ ./configure --prefix=/opt/quilt
  $ make
  $ make check

Step 2: tag the new version
---------------------------

- $ git add configure.ac configure NEWS
  $ git commit -m "Set version to x.y."
  $ git tag vx.y
  $ git push
  $ git push --tags

Step 3: publish the new version
-------------------------------

- If not done already:
  $ ./configure --prefix=/opt/quilt
- If you have multiple PGP keys, make sure the right one is selected.
- $ make publish