On Friday 04 June 2010 17:30:03 Ben Finney wrote: > Gianluca Montecchi <[email protected]> writes: > > On Fri, Jun 04, 2010 at 10:11:59AM -0400, Chris Ball wrote: > > > What's the advantage of having them out of sync? > > > > Just to say the first that cross my mind: the possibility to publish > > on the web a complete list of bugs for a project, where it is logical > > to publish all the bugs from all the branches. > > The different branches will have bugs in different states.
Of course > So you have to pick one branch to be the canonical version of the bug > database. To my understanding, it should be the branch that is also the > canonical “trunk” branch for the code. > > What am I missing? As I see it, you are missing that you can have more than one branch that can be published. Think about a stable branch and a development branch. you shold want to publish the two bugs databases. I agree that they can be see as two different db, but I think that if a project has more than one database to be published, there should be some way to glue them together, at least in read only mode. I agree that we can use the approach Trevor suggested. bye Gianluca _______________________________________________ Be-devel mailing list [email protected] http://void.printf.net/cgi-bin/mailman/listinfo/be-devel
