[p4dti-discussion] Upgrading Bugzilla, Perforce, and DT[IG]

[Nick Barnes]

At 2008-05-08 00:43:17+0000, alex.pavloff at l-3com.com writes:

> Bugzilla 3.1.x (and all odd minor version numbers) are the test releases
> that lead to the next release (3.1.x will become 3.2.x).  
> 
> 3.0 is the latest stable version, and the one you should use for
> production systems.  
> 
> I have no idea what Perforce and Ravenbrook's plans are, but I wouldn't
> doubt that a new version of the P4DTI that supports 3.2 is released
> after the official release of Bugzilla 3.2.

Exactly so.  Thank you, Alex.

The current P4DTI release (2.4.2) was made shortly after the release
of Bugzilla 3.0, and works with all Bugzilla 3.0.x releases including
this week's 3.0.4.

As you can see at <http://www.bugzilla.org/releases/>, the 3.1.x
releases are development snapshots.  As it happens, P4DTI 2.4.2 can be
made to work with Bugzilla 3.1.x -- although it requires customisation
to handle some post-3.0 Bugzilla features (custom workflow,
multi-select custom fields, the bugs_fulltext table which speeds up
full text searching in 3.1.4) -- but such use is not supported.

Bugzilla 3.2rc1 is expected very shortly, and I expect to start
working on Bugzilla 3.2 support in the P4DTI after that.  We are
watching the changes in the Bugzilla trunk and development releases
with interest, and tracking them in our online Bugzilla schema
documentation <http://www.ravenbrook.com/project/p4dti/tool/cgi/bugzilla-schema/>,
but we have a long-standing policy of not supporting development
or beta releases of third-party software (e.g. MySQL 5.1 is not
supported).

This doesn't fit entirely well with the habit of some Linux
distributions of shipping development or beta versions of third-party
software by default (e.g. MySQL 5.0.x packages were the default in
many Linux distros long before 5.0 came out of beta, and some now
default to 5.1.x which is still in beta).  But tracking every latest
beta or experimental release of everything is a fool's errand.  So we
need some policy to limit this, and the policy is that beta and
development releases are not supported.

Nick Barnes
P4DTI Project
Ravenbrook Limited