Mongodb 3.4 is out so we should stabilize 3.2, what do you think?
We need to either target 3.4 for stable or backport a patch from 3.4, for bug 626342. I don't see any regressions for 3.4
Any word from maintainers on this? Ok to start stable process & CC arches?
(In reply to Ben Kohler from comment #2) > Any word from maintainers on this? Ok to start stable process & CC arches? First we need to merge https://github.com/gentoo/gentoo/pull/5527
(In reply to Tomáš Mózes from comment #3) > (In reply to Ben Kohler from comment #2) > > Any word from maintainers on this? Ok to start stable process & CC arches? > > First we need to merge https://github.com/gentoo/gentoo/pull/5527 That was done yesterday ;)
when will 3.2 be stabled, we'd like to try some new feature, thanks.
(In reply to Zhixu Liu from comment #5) > when will 3.2 be stabled, we'd like to try some new feature, thanks. You can add mongodb-3.2 to package.accept_keywords until it's stabilized and then emerge it on a stable system.
Let's move on, arches please proceed! Thanks a lot
Stable on amd64.
x86 stopped stabilization due to bug 647184.
Just wondering, how long can a stable request be in limbo? Did someone forget this or why status IN_PROGRESS? Just trying to figure this out :p Making 3.2.17 stable does not make any sense anymore. or?
Yes, closing this as it won't be stabilized on x86 any more. Will continue with mongodb 3.6 stabilization. Thanks.