blob: 7385e4d9b121bd1c69f54078fe1b9bfce8f96541 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
|
eselect Release Guide
======================
.. Note:: This guide is intended for people who do ``eselect`` releases. It is
probably of no interest to the rest of you.
Make sure ChangeLog is tidy. Add ChangeLog entry for updating configure.in
and tagging the release.
Update NEWS file with a summary of changes mentioned in ChangeLog since the
last release.
Do a test run in trunk/. ::
$ ./autogen.sh
$ ./configure
$ make dist
$ mv ${P}.tar.bz2 ${DISTDIR}
Test with an ebuild and make sure everything builds and everything that
should be included in the tarball is.
Test eselect itself and as many modules as you can.
Commit any changes you may have made in the previous steps.
Tag release. ::
$ make maintainer-clean
$ svn copy trunk tags/release-${PV}
$ svn commit -m "Tagged ${PV} release."
Build the final tarball. ::
$ cd tags/release-${PV}
$ ./autogen.sh
$ ./configure
$ make dist-bzip2
Sign it (there may be a dist-sign target in the future). ::
$ gpg --armor --detach-sign ${P}.tar.bz2
Release.
1) Log into your berlios account.
2) Go to the Admin section of eselect project page.
3) Go to Edit/Add File Releases
4) Scroll to bottom and find eselect project. click on 'Add Release'.
5) Upload tarball and gpg signature to ftp.berlios.de/incoming (login
as anonymous) via your favorite ftp client.
6) In 'New release name:' text box, put ${PV}. 'Of which package' should
be eselect. Click on Create This Release.
7) Paste the summary you added to NEWS in the ChangeLog box and select
'Preserve my pre-formatted text'
8) Scroll down and find the two files you uploaded and select them. Click
'Add files and/or Refresh View'.
9) Scroll down to Step 3 and select 'Any' Processor and 'Text' for the
signature and 'Any' Processor 'Source .bz2' for the tarball (can only
do one at a time though inbetween updating).
10) If you're doing the ebuild, then follow normal version bump steps from here.
.. vim: set ft=glep tw=80 sw=4 et spell spelllang=en : ..
|
GitWeb
