[phpBT-dev] Project Heirachies

[Brent R. <br...@mb...>]

This is a feature request from a user of phpBT v0.51.
It doesn't appear to be in the current version either, but I have only
read the docs for v0.9x on the web -- not installed it to test.

What do you think of it?
Is is already present in the current version?
If not, would it be considered?
Are the better ways to get the same effect?

In a nutshell, this user wants project hierarchies where projects are 
made up
of components, each of which may be viewed as a project in their own right.

Here's the original "bug" this user filed against phpbt in our phpbt 
database :-)
------------------

The version tracking model in phpbt seems insufficient. While tracking 
bugs against major project releases is an important feature, it is also 
necessary to track bugs against releases of individual components. (On 
some projects, components may be updated many times without having a new 
version of the overall project. Other projects may bundle many different 
kinds of components, which may not be tightly coupled to 'project' 
progress at all.)

There are workarounds which can get us by in the short term. For a VARS 
component, I called the version "VCR yymmdd", encoding the component 
name in the version ID. This is functional, but cumbersome, and not 
suitable for larger projects with many components. Another option would 
be to use a standard syntax for versioning components, e.g., 
ProjectVersion.ComponentVersion (so all components would start at x.1, 
then x.2, etc). This ends up being a little awkward as well, and you're 
still encoding the project version in the same field, which is a little 
bogus.

Soo, although it's probably a lot of work, Component versioning is 
something the phpbg folks need to support.

-- 
 Brent Roman                                   MBARI
 Software Engineer               Tel: (831) 775-1808
 7700 Sandholdt Road,         Moss Landing, CA 95039
 mailto:br...@mb...  http://www.mbari.org/~brent