aboutsummaryrefslogtreecommitdiffstats
path: root/.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/381555eb-f2e3-4ef0-8303-d759c00b390a/comments/9aa88bbd-71d0-44fa-804d-3562171f9539
diff options
context:
space:
mode:
authorW. Trevor King <wking@drexel.edu>2012-02-16 11:57:31 -0500
committerW. Trevor King <wking@drexel.edu>2012-02-16 11:57:35 -0500
commit0d3d9a3780a27f1c80833638ad0622bf4e67023d (patch)
treeaa81caa61cb294246aef4b2d9fc7266c572509e1 /.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/381555eb-f2e3-4ef0-8303-d759c00b390a/comments/9aa88bbd-71d0-44fa-804d-3562171f9539
parent89dc85d66b1ce98705206b6e492dc6302f843b97 (diff)
downloadbugseverywhere-0d3d9a3780a27f1c80833638ad0622bf4e67023d.tar.gz
Fix release.py to allow uncommented initial _VERSION.
I was in favor of always leaving _VERSION commented in the trunk, since released branches should fork off the trunk: trunkA -> trunkB -> trunkC -> trunkD `-> 1.0.0 `-> 1.1.0 `-> 1.0.1 `-> 1.1.1 But that doesn't seem to have been how things have worked out in BE. In any case, you will need to release on top of a previous release (e.g. 1.0.1 on top of 1.0.0 in my above example), so we cannot depend on an initial comment character before _VERSION.
Diffstat (limited to '.be/bea86499-824e-4e77-b085-2d581fa9ccab/bugs/381555eb-f2e3-4ef0-8303-d759c00b390a/comments/9aa88bbd-71d0-44fa-804d-3562171f9539')
0 files changed, 0 insertions, 0 deletions