@@ -25,3 +25,28 @@ with them do::
25
25
26
26
The actual Python compilation is only done once and then re-used. So on
27
27
subsequent builds, only the development buildout itself needs to be redone.
28
+
29
+
30
+ Releases: zc.buildout, zc.recipe.egg and bootstrap.py
31
+ -----------------------------------------------------
32
+
33
+ Buildout consists of two python packages that are released separately:
34
+ zc.buildout and zc.recipe.egg. zc.recipe.egg is changed much less often than
35
+ zc.buildout.
36
+
37
+ zc.buildout's setup.py and changelog is in the same directory as this
38
+ ``DEVELOPERS.txt`` and the code is in ``src/zc/buildout``.
39
+
40
+ zc.recipe.egg, including setup.py and a separate changelog, is in the
41
+ ``zc.recipe.egg_`` subdirectory.
42
+
43
+ A third item is the bootstrap.py file in ``bootstrap/bootstrap.py``. The
44
+ canonical location is at https://bootstrap.pypa.io/bootstrap-buildout.py,
45
+ (though it is unfortunate that it isn't named just ``bootstrap.py``). This
46
+ file is pulled automatically every 15 minutes from the bootstrap-release
47
+ branch. When a new buildout release is made, **the releaser** should update
48
+ the bootstrap-release branch, too.
49
+
50
+ The http://downloads.buildout.org/2/bootstrap.py location doesn't need to be
51
+ updated manually: it is a redirect now, to
52
+ https://bootstrap.pypa.io/bootstrap-buildout.py .
0 commit comments