summaryrefslogtreecommitdiffstats
path: root/HOWTO/subrelease.txt
blob: fbba52a29666fc957a2c3b5fde3bd7370a153ad3 (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
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
__COPYRIGHT__

This document covers how to prepare subreleases of SCons--that is,
releases numbered with X.Y.Z format, such as 0.94.1, 1.0.1, etc.

If you need to prepare a release (X.Y, such as 0.93, 1.0, etc.), then
see the document HOWTO/release.txt.

Things to do to release a new X.Y.Z version of SCons:

    START THE NEW SUB-BRANCH FOR SUBRELEASE

        aenbr -p scons.0.{94} {1}

        aenc -p scons.0.{94}.{1}

            Call it something like,
            "Prepare a new sub-release for XYZ."
            Cause = internal_enhancement.
            Exempt it from all tests (*_exempt = true).

        ae_p scons.0.{94}.{1}

        aedb 100

        aecd

        # Change the hard-coded package version numbers
        # in the following files.
        aecp README
        vi README

        aecp SConstruct
        vi SConstruct

        aecp rpm/scons.spec.in
        vi rpm/scons.spec.in

        aecp src/setup.py
        vi src/setup.py

        aecp QMTest/TestSCons.py
        vi QMTest/TestSCons.py

        # Read through and update the README files if necessary
        [optional] aecp README
        [optional] vi README

        [optional] aecp src/README.txt
        [optional] vi src/README.txt

        # Prepare src/CHANGES.txt
        aecp src/CHANGES.txt
        vi src/CHANGES.txt

            change the release line to reflect
            the new subrelease

            date -R the new subrelease

            add an explanatory not after the subrelease line:

                    NOTE:  This is a pre-release of 0.{95}
                    for testing purposes.  When 0.{95} is
                    released, all these changes will show
                    up as 0.95 changes.

        # Prepare src/RELEASE.txt
        aecp src/RELEASE.txt
        vi src/RELEASE.txt

            date -R the release only if necessary

            Read through and edit appropriately.

            Can probably keep most of the existing text

            Add any new known problems

        # Prepare debian/changelog
        aecp debian/changelog
        vi debian/changelog

            add the new subrelease

            date -R the new subrelease

        # Now build and prepare the release itself.
        aeb

        aet -reg

        aed

        aede

        etc.



    Make the relevant packages available for by-hand pickup directly
    off the web site:

        scp scons-0.{94}.{1}.tar.gz stevenknight@scons.sourceforge.net:/home/groups/s/sc/scons/htdocs
        scp scons-0.{94}.{1}.zip stevenknight@scons.sourceforge.net:/home/groups/s/sc/scons/htdocs


    Test downloading from the web site.



    Announce to dev@scons.tigris.org.