Subject: Re: [boost] [test] Looking for co-developer/maintainer
From: Gennadiy Rozental (rogeeff_at_[hidden])
Date: 2014-01-24 11:09:11
Andrey Semashev <andrey.semashev <at> gmail.com> writes:
> I'd like to point out that if a bug has been fixed in trunk/develop
> but the fix has not been merged to release/master, the bugfix is not
> delivered to users and is as good as not fixed.
That's why ticket is not closed.
> If you fixed a bug in
> trunk but didn't find a chance to merge the fix to release for years
> then you clearly don't have the resources to properly maintain the
> library. "It's been fixed in trunk" is not an excuse.
I think you not exactly appreciate amount of time/effort it require to push
the change in core library to release branch. Regardless of number of
maintainers, this is still has a significant probability of being disruptive
and I decided not pursue it unlesss I have a lot of time time to address the
issues and really good reason to back up the change. The best policy is to
push changes in batches, but now Iam stuck, since I can't push latest changes
till I document them.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk