Thanks Marek, that does clear up a lot of confusion.
I think you're saying that because the maintainer is the same and the packages
are essentially the same (in this case), it's reasonably likely maintenance of
2.6 for EPEL7 will continue until 2.6 reaches its end date in SCL (April 2018).
Not
"What I am saying is that EPEL is made up of volunteers. If you are
volunteering to do this work then great. If you are expecting that
someone else is going to do this work for you.. then not so great."
Oh, absolutely. I'm not under the slightest illusion that anybody owes me
maintenance of an
I see. Since MongoDB is under a GNU license, I assume you do not literally mean
you have zero access to the changes being made to it in SCL. My assumption is
that you actually mean there's no advanced or privileged access. So if some bad
juju goes down, and we want to look to SCL For help,
Stephen, good question... I was looking here:
https://www.softwarecollections.org/en/scls/rhscl/rh-mongodb26/
Which came up first in Google for rhsc mongodb, but that's not right. I should
have been looking here:
https://access.redhat.com/support/policy/updates/rhscl
The Software Collections
Sorry, I just saw the part about RHSCL. But that page says:
"Community Project: Maintained by upstream communities of developers. The
software is cared for, but the developers make no commitments to update the
repositories in a timely manner."
S... is there actually a commitment from Red
I think that if a CVE arrives that we can't easily address through a patch, we
have to be prepared to force an upgrade. Potentially "abandoning" a package
that has CVEs in the wild, in the hope people will read about an optional
upgrade, sounds like a policy we could regret.
Is there any
Oops, I've copied my reply to the EPEL list as requested.
On Mon, Oct 31, 2016 at 1:17 PM, Tom Boutell <t...@punkave.com> wrote:
> There is no version 2.8 of Mongo, they renamed that to 3.0 before release of
> 3.0.
>
> Just to provide a sense of the thought process other
There is no version 2.8 of Mongo, they renamed that to 3.0 before release of
3.0.
Just to provide a sense of the thought process other EPEL7 users might be going
through here:
I started researching this when I became aware that 2.6 was nearing upstream
end-of-life (that is now happening
