Boost logo

Boost :

From: Joaquín Mª López Muñoz (joaquin_at_[hidden])
Date: 2004-08-26 08:09:30


Aleksey Gurtovoy ha escrito:

> JOAQUIN LOPEZ MU?Z writes:
> > I don't want to sound harsh or anything, and I truly
> > appreciate the effort that's being put in this, but
> > a month has slipped by since the first schedule for
> > releasing, and AFAIK we don't even have an agreed upon
> > branching date for the near future.
>
> The branching date is pending MPL check-in. The latter has
> been postponed several times as the new issues surfaced (in
> particular, due to better tests), but it's crucial to ensure
> that the library is in the predictable state before the
> release (remember that it goes on the CD with the TMP book),
> so please bear with us.
>
> > People are beginning
> > to divert (a review in progress, etc.) I haven't been
> > involved in previous releases, but I guess a month
> > delay is well over what's considered normal/acceptable.
>
> There are external constraints for this release's timeframe,
> but within those, the release is criteria-driven. One of the
> criteria is regression-free codebase, and another is the new
> MPL version. There is no point of releasing "on time" if the
> release is useless.
>

I hope you haven't thought I'm irritated or trying to attack ayone; I've
tried to write my post in the sweetest manner my English skills allow me,
if it felt flaming I apologize, that was not my intention.

Only that from my rather external point of view things didn't seem to
have changed much during the last three weeks or so, no feedback
or progress at all. But at least now from your answers and Dave's we have
some concrete info, namely that branching will occur after MPL is checked
in and that there's the absolute CD deadline. And I know you're working
hard at this. That's fine.

And I can't but agree on your concern about the general status of the
regression tests, of which the MPL issue is not responsible.

>
> >
> > Shouldn't we settle now on a realistic branching date
> > and proceed with the release? Or, should I shut my mouth
> > and let the release manager handle this as he deems
> > convenient?
> >
> > Again, don't get me wrong. I am not willing to push
> > anybody, but the process looks, well, erratic.
>
> Please don't forget that we are all volunteers here. The best
> way to speed up things is to contribute to them. MPL issues
> notwithstanding, we still have the regression field to be
> cleared --
> http://www.meta-comm.com/engineering/boost-regression/developer/summary.html.
> Turning it green while MPL is in works will make a huge
> difference. If you are willing to take over managing that one
> until the MPL check-in, be my guest.
>

I whish I could, but I'm already stealing much too time from my daily
work to engage into managerial tasks. OTOH I've done little contributions
to some problems before vacation, and will try to help a bit now.

Again, please do not take my complaints as offence. I much
appreciate your volunteering to manage the release and wouldn't
want to be seen as an additional source of pressure.

Best,

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk