Subject: Re: [boost] Maintenance suspended
From: Hartmut Kaiser (hartmut.kaiser_at_[hidden])
Date: 2010-07-07 18:13:01
> > Do you have somebody replacing you while in suspension?
> Not formally. I have co-maintainers on most of my libraries, and
> Boost.Python maintenance has mostly been done by others (especially Ralf
> Grosse-Kunstleve) for well over a year now.
Boost has a clear policy of what has to happen if a maintainer wants to give
up (or to take a break as you say below).
One of the points is that it has to be ensured maintenance is taken over by
somebody else, see:
What will happen to the libraries you don't have a co-maintainer for?
> > I can't say agree with your decision, even while I feel your pain. We
> > all have to live with the current setup but nevertheless we can't and
> > do not just throw the towel.
> I'm not throwing in the towel; I'm taking a break.
Nice try. But using a different term doesn't change anything.
If somebody else were to write such an email you would be the first to
> > It's a comparably minor exercise in patience to do the merge (btw, I
> > just spend 3 days merging Spirit to the release branch, so believe me,
> > I know what you're talking about). It's minor if compared to the
> > effort which is still required to make Ryppl a commonplace tool. And,
> > it will take another release cycle or two to have the move completed.
> > So, I would like to ask you to rethink this decision once more. If
> > everybody did as you plan to do, we would blow this release.
> My libraries are mostly fairly mature. While there are things that should
> be improved, there's no reason that not making changes should cause the
> release to be blown.
This seems to be illogical to me. If your libraries were stable and mature,
then not suspending maintenance wouldn't add any work to your schedule.
But I shut up on this as it seems I'm the only one feeling to be cheated on.
Meet me at BoostCon