This repository has been archived by the owner on Jan 25, 2019. It is now read-only.
/
CHANGES.txt
72 lines (44 loc) · 1.54 KB
/
CHANGES.txt
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
Changelog
=========
0.0.7 (unreleased)
------------------
- Nothing changed yet.
0.0.6 (2012-04-08)
------------------
- Nothing changed yet.
0.0.5 (2012-04-07)
------------------
- Don't include empty mappings in output
0.0.4 (2012-04-03)
------------------
- Process command line options first.
0.0.3 (2012-03-20)
------------------
- Now supports tracking maximum versions of fields::
[postdeploy]
history.track =
environment:zopes max
The default tracking action is called ``removed``.
In this example, ``history.environment.zopes`` would be the largest number of
zopes this buildout deployment has had. The use case for this is that your
buildout just destroyed the start/stop scripts for those olds zopes and you
want to make sure they were actually stopped. I could then do something like
this from my Yaybu configuration::
.foreach i in range(buildout.environment.zopes, history.environment.zopes):
- Execute:
name: stop-forgotten-zope-${i}
command: kill-command zope${i}
unless: some-manual-pid-check
0.0.2 (2012-03-17)
------------------
- Any sections that are simple metadata and not referenced from a part will now
be available in postdeploy configuration. Note that if a section isn't
referenced by an installed part and uses variables then it can't be included:
the act of inspecting it might cause additional buildout recipes to be
executed.
0.0.1 (2012-03-16)
------------------
- Fix packaging
0.0.0 (2012-03-16)
------------------
- Initial release.