Bug #7357: Is there an ETA for 3.5.3?

1 post / 0 new
#1 Wed, 2017-09-06 01:14
  • spencerwilson-optimizely's picture
  • Offline
  • Last seen: 4 months 2 weeks ago
  • Joined: 2017-09-06

Hi all,

First off, thank you for the work you all put into maintaining Alpine. It is appreciated.

I was wondering when the 3.5.x branch might see its next release? A few CVEs had their fix merged 3 months ago (http://bugs.alpinelinux.org/issues/7357), but haven't yet seen release. I understand there is in general no firm release cadence; just am wondering if there is an estimate available on when might be released.

Our use case: our Docker application is based on mhart/alpine-node:7, which is based on alpine:3.5 (If you're curious, the official node:alpine-7 is on alpine:3.4, so is even older). Neither of which are likely maintained, as Node.js 7.x is not maintained. Images based on mhart/alpine-node:7 that are scanned with a security tool like Twistlock report a few of the vulnerabilities that were addressed in the above-linked bug.

Thanks in advance!