aboutsummaryrefslogtreecommitdiffstats
path: root/.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/0c40c13a-3515-4b45-a8c3-142cceab9254
diff options
context:
space:
mode:
Diffstat (limited to '.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/0c40c13a-3515-4b45-a8c3-142cceab9254')
-rw-r--r--.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/0c40c13a-3515-4b45-a8c3-142cceab9254/body36
-rw-r--r--.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/0c40c13a-3515-4b45-a8c3-142cceab9254/values14
2 files changed, 0 insertions, 50 deletions
diff --git a/.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/0c40c13a-3515-4b45-a8c3-142cceab9254/body b/.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/0c40c13a-3515-4b45-a8c3-142cceab9254/body
deleted file mode 100644
index fa9e963..0000000
--- a/.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/0c40c13a-3515-4b45-a8c3-142cceab9254/body
+++ /dev/null
@@ -1,36 +0,0 @@
-* W. Trevor King (wking@drexel.edu) wrote:
-> One problem is that we don't actually have "releases". People just
-> clone a branch, install, and go.
-
- This is actually the main reason I've manually mirrored the tree in
-the past, so that users of our projects can get BE. If tarballs were
-available I probably wouldn't even bother, but bzr really isn't a nice
-dependency for just submitting/commenting on bugs.
-
- Isn't there a bzr web interface that at least supports creating
-tarballs/zips? It is pretty standard functionality for most other VCS'
-web interfaces so I'm guessing there must be, but loggerhead seems not
-to support it.
-
- If it is a case of not having the hardware to host a more featureful
-web UI I may be able to offer some assistance.
-
-> If you're worried about stability, just clone from a more stable branch
-> (i.e., Chris' trunk). I think > this is good for distributed development,
-> but maybe makes it hard to package into a conventional release-based system.
-> With the bzr patch number in setup.py as the patch release number, I would be
-> releasing my 0.1.363 while Chris releases his 0.1.314, even though they're at
-> about the same point. I would rather be releasing my
-> 0.1.20090714121347
-> while Chris releases his
-> 0.1.20090713154540
-> Since then the similarity is clearer.
-
- Both approaches seem pretty odd to me, as a user you would have no
-idea if 0.1.200910302359 has the fixes you required in a release you
-were using that was numbered 0.1.200907141554. Surely you'd at least be
-{pre,suf}fixing a branch name to the version.
-
-Thanks,
-
-James
diff --git a/.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/0c40c13a-3515-4b45-a8c3-142cceab9254/values b/.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/0c40c13a-3515-4b45-a8c3-142cceab9254/values
deleted file mode 100644
index e7077e7..0000000
--- a/.be/bugs/529c290e-b1cf-4800-be7e-68f1ecb9565c/comments/0c40c13a-3515-4b45-a8c3-142cceab9254/values
+++ /dev/null
@@ -1,14 +0,0 @@
-Alt-id: <20090714142942.GA5717@ukfsn.org>
-
-
-Author: James Rowe <jnrowe@gmail.com>
-
-
-Content-type: text/plain
-
-
-Date: Tue, 14 Jul 2009 15:29:42 +0100
-
-
-In-reply-to: ea01c122-e629-4d5c-afa7-b180f4a8748b
-