blob: 6cbe7d98da29f40441e32625935e538d694e404b [file] [log] [blame]
Tim Petersfc9eeae2000-09-07 08:28:50 +00001Python has a "build number" scheme on Unix-like systems that's hard to
2explain:
3
4Python 2.0b1 (#4, Sep 7 2000, 02:40:55) [MSC 32 bit (Intel)] on win32
5 ^^
6The build number there is "#4".
7
8Each developer's unique build tree generates its own "build numbers",
9starting at 0, and increasing by 1 each time a build is done in that tree.
10These numbers are never checked in, or coordinated in any other way. It's
11just handy for a developer to distinguish among their own personal builds.
12
13The makefile tricks used to accomplish this under Unix-like systems don't
14work under MSDev. Here we fake it by hand, but much less frequently, and
15do check it in. The build number only changes often enough to distinguish
16releases from each other, and from the long "in between" stretches of CVS
17development. An account of all Windows BUILD numbers follows; when you
18check in a new one, please add an entry to the top of the list.
19
20How to change the Windows build number:
21
22+ Right-click on getbuildinfo.c from within MSDev. Select Settings ...
23+ Select the General category of the C/C++ tab.
24+ In "Settings For:" select "Multiple Configurations ...".
25+ Check the "Win32 Release" and "Win32 Debug" boxes and click OK.
26+ In the Preprocessor Definitions box, increment the number after BUILD=.
27+ Click OK.
28+ This is not enough to convince MSDev to recompile getbuildinfo.c,
29 so force that and relink.
Tim Peters68692452000-10-14 07:35:15 +000030+ Verify that the new build number shows up in both release and debug
Tim Petersfc9eeae2000-09-07 08:28:50 +000031 builds.
32
33
34Windows Python BUILD numbers
35----------------------------
Tim Peters52709e32001-04-18 21:12:25 +000036 16 CVS development
37 18-Apr-2001
38 15 2.1 final
Tim Petersdd37dac2001-04-16 18:20:30 +000039 16-Apr-2001
Tim Petersb0931662001-04-16 01:44:08 +000040 14 2.1c2
41 15-Apr-2001
Tim Petersfd09e862001-04-12 04:01:39 +000042 13 2.1c1
43 12-Apr-2001
Tim Peters55f826c2001-03-21 06:09:14 +000044 12 2.1b2
45 20-Mar-2001
Tim Peters5f850ab2001-03-01 02:43:40 +000046 11 2.1b1
47 28-Feb-2001
Tim Petersca873ed2001-02-01 05:10:02 +000048 10 2.1a2
49 1-Feb-2001
Tim Peters97c96402001-01-17 23:23:13 +000050 9 2.1a1
51 17-Jan-2001
Tim Peters68692452000-10-14 07:35:15 +000052 8 2.0 (final)
53 14-Oct-2000
Tim Peters70d87d72000-10-07 04:04:07 +000054 7 2.0c1
55 07-Oct-2000
Tim Petersf1fcc812000-09-25 21:55:28 +000056 6 2.0b2
57 26-Sep-2000
Tim Petersfc9eeae2000-09-07 08:28:50 +000058 5 CVS development
59 07-Sep-2000
60 4 2.0b1 repaired to include Lib\xml + Lib\lib-old + Lib\test\*.xml
61 07-Sep-2000
62 3 2.0b1
63 05-Sep-2000
64 2 CVS development
65 1 unused
66 0 2.0b1p1 and 2.0b1p2
67 01-Sep-2000 for both -- this scheme hadn't started yet