Boost Testing :
From: Boris Gubenko (Boris.Gubenko_at_[hidden])
Date: 2006-06-07 18:40:57
> This scheme implies that regression tests are run continuously
> not only when the release is approaching at least for required
I understand. We were late in the game for 1.34.
I realize, that no HP-UX - specific patches will be added to 1.34 at
this point, but we'll need to continue to test RC_1_34_0 branch to get
understanding what the problems with this release are and what
workaround(s) we can recommend to the customer(s).
We'll also be running tests against CVS HEAD to be better prepared
----- Original Message -----
From: "JOAQUIN LOPEZ MU?Z" <joaquin_at_[hidden]>
Cc: "Boris Gubenko" <Boris.Gubenko_at_[hidden]>
Sent: Wednesday, June 07, 2006 5:19 PM
Subject: Re: [Boost-testing] Missing toolsets from 1.33.1 to 1.34
----- Mensaje original -----
De: Boris Gubenko <Boris.Gubenko_at_[hidden]>
Fecha: Miércoles, Junio 7, 2006 9:57 pm
Asunto: Re: [Boost-testing] Missing toolsets from 1.33.1 to 1.34
> For the past couple of days, we've been running boost tests for the
> RC_1_34_0 branch on HP-UX ia64 with aCC A.06.10 compiler.
Hello Boris, thank you for your contribution!
> The results are on the web in the Full View (I guess, they are
> not in Release View because HP-UX/aCC6 is not a required platform
> for the 1.34 release).
This is correct: release view only shows required platforms.
> The results do not look bad, but there are some failures that need to
> be investigated before we can ask to consider HP-UX/aCC6 a supported
> platform for boost.
In any case, you cannot ask for HP-UX/aCC6 to be promoted
to "required platform" status for Boost 1.34, as the list
has just been closed:
you might want to propose it in Boost 1.35.
> We'll continue to be running the tests against RC_1_34_0 on a regular
> basis and, at some point, I think, we'll need to switch to CVS HEAD
> to be part of the new boost release. Perhaps, this is too early to
> ask, but anyway: was it already decided what the release after 1.34
> is going to be and what would be a timeframe for this release?
I don't think there's any estimated date yet. What seems
likely, though, is that the release procedure will undergo
some major changes, like switching to SVN and trying a
different release model hopefully guaranteeing an always-ready
release branch, see
This scheme implies that regression tests are run continuously,
not only when the release is approaching, at least for required
Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo