diff options
| author | W. Trevor King <wking@drexel.edu> | 2009-12-13 06:19:23 -0500 |
|---|---|---|
| committer | W. Trevor King <wking@drexel.edu> | 2009-12-13 06:19:23 -0500 |
| commit | 4d057dab603f42ec40b911dbee6792dcf107bd14 (patch) | |
| tree | 9a73459aa160e3c96f4893b132543f412ca6e97f /.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/744435b7-1521-4059-a55d-f0c403d7b4d8 | |
| parent | dff6bd9bf89ca80e2265696a478e540476718c9c (diff) | |
| download | bugseverywhere-4d057dab603f42ec40b911dbee6792dcf107bd14.tar.gz | |
Converted libbe.storage.vcs.base to new Storage format.
Diffstat (limited to '.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/744435b7-1521-4059-a55d-f0c403d7b4d8')
2 files changed, 0 insertions, 72 deletions
diff --git a/.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/744435b7-1521-4059-a55d-f0c403d7b4d8/body b/.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/744435b7-1521-4059-a55d-f0c403d7b4d8/body deleted file mode 100644 index 24ff7b0..0000000 --- a/.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/744435b7-1521-4059-a55d-f0c403d7b4d8/body +++ /dev/null @@ -1,58 +0,0 @@ -"W. Trevor King" <wking@drexel.edu> writes: - -> Currently setup.py sets the version number for BE to 0.0.193 and the -> url to http://panoramicfeedback.com/opensource/. These are both a bit -> outdated ;). - -Right, that should change. - -> I've switched my branch over to the current url, and moved to -> last-commit-timestamp version numbers. - -Please, no. Timestamps aren't version strings, that's conflating two -pieces of information with very different meanings. Correlating the two -is the job of a changelog. - -> This removes the "prefered branch" issues with the old scheme, and -> version numbers should increase monotonically - -The English word “should” is ambiguous in this context. Are you saying -this is desirable, or are you predicting that it will likely be the -case? - -I don't see how it's either, so am doubly confused :-) - -> but it looses any stability information suggested by the preceding -> 0.0. - -The convention for three-part version strings is often: - - * Major release number (big changes in how the program works, - increasing monotonically per major release, with “0”indicating no - major release yet) - - * Minor release number (smaller impact on how the program works, - increasing monotonically per minor release, with “0” indicating no - minor release yet since the previous major) - - * Patch release number (bug-fix and other changes that don't affect - the documented interface, increasing monotonically per patch - release, with “0” indicating no patch release since the previous - major or minor) - -Obviously there's no standard or enforcement for this, but that's the -interpretation I usually give to dotted version strings in the absence -of more formal declaration specific to the project. - -> We can add those back in if people want. Does the first 0 mean -> "interfaces in flux" and the second 0 mean "lots of bugs"? If so, I -> think we're up to 0.1, since the major features are pretty calm. - -I disagree with your interpretation and prefer mine, above; on that -basis, I agree that we're at least up to version 0.1 by now :-) - --- - \ “A lot of water has been passed under the bridge since this | - `\ variation has been played.” chess book, Russia | -_o__) | -Ben Finney diff --git a/.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/744435b7-1521-4059-a55d-f0c403d7b4d8/values b/.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/744435b7-1521-4059-a55d-f0c403d7b4d8/values deleted file mode 100644 index c5d9cbb..0000000 --- a/.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/744435b7-1521-4059-a55d-f0c403d7b4d8/values +++ /dev/null @@ -1,14 +0,0 @@ -Alt-id: <87ocrnjvat.fsf@benfinney.id.au> - - -Author: Ben Finney <bignose+hates-spam@benfinney.id.au> - - -Content-type: text/plain - - -Date: Tue, 14 Jul 2009 22:36:26 +1000 - - -In-reply-to: cdf15bdd-d3fe-4251-9d0b-f1b687e9a26c - |