blob: 3b417bedb7d30aa85632eb0b46da9cc3539f73e4 (
plain) (
blame)
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
|
On Sat, 2009-07-11 at 08:50 -0400, W. Trevor King wrote:
> On Sat, Jul 11, 2009 at 01:54:54PM +0200, Ronny Pfannschmidt wrote:
> > 1. is there any way to aggregate over multiple public branches in order
> > to get the complete bug state
>
> Keeping the bug data with the source helps synchronize bug state and
> source code. Bug state in branch A may not apply to branch B. Some
> people like to weaken this source-bug linkage by keeping their bugs in
> a branch all by themselves (ditz [http://ditz.rubyforge.org/]
> currently supports this workflow). It sounds like you want to move
> from "bugs with code" to "bugs and code in separate branches". We
> don't have an easy way to do that in BE at the moment, since
> version-control systems like Git have a single working branch at a
> time (I think :p). What VCS are you using as a backend?
the basic idea is to take a look at all public branches (for exaple all
on lp/bitbucket/github) in order to tell the user of a webinterface that
bug foo is fixed in branch xyz, and if its merged to the main branch
>
> > 2. is there any model for storing bigger files at a central place (for
> > some of my bugs i have multi-megabyte tarballs attached)
>
> be comment ID "See the tarball at http://yourpage/something.tar.gz"
> Then to grab the tarball, you'd use:
> wget `be show COMMENT-ID | sed -n 's/ *See the tarball at //p'`
> to grab it.
so the basic idea is to do it completely self-managed and have have
heterogenous sources of extended data?
|
