v3.4 contains important security fixes for CVE-2018-1098 CVE-2018-1099.
Could you consider making a release for that branch? Thanks in advance.
zumbi
All 2 comments
As I can see v3.4 would also fix issues with import paths https://github.com/etcd-io/etcd/issues/10410
ivanovaleksey
on 19 Feb 2019
@ivanovaleksey @zumbi I understand your concerns. You can review the progress on 3.4 here. Until the community agrees on a final feature set and we complete that 3.4 won't be released. In our last community meeting we discussed the possibility of reducing the number of features in 3.4. Saying that I don't see a release until Summer 19 earliest, we all want to get there but we can't make the cut hastily. Saying that if you see an issue you would like to help on it would be a step towards realizing 3.4!
We will consider backporting CVE-2018-1098 CVE-2018-1099, lets track that here https://github.com/etcd-io/etcd/issues/10479.
hexfusion
on 19 Feb 2019
Related issues
hnlq715
路
3Comments
invidian
路
3Comments
suresh-chaudhari
路
3Comments
r007m4n
路
3Comments
itnikita
路
3Comments
Most helpful comment
@ivanovaleksey @zumbi I understand your concerns. You can review the progress on 3.4 here. Until the community agrees on a final feature set and we complete that 3.4 won't be released. In our last community meeting we discussed the possibility of reducing the number of features in 3.4. Saying that I don't see a release until Summer 19 earliest, we all want to get there but we can't make the cut hastily. Saying that if you see an issue you would like to help on it would be a step towards realizing 3.4!
We will consider backporting CVE-2018-1098 CVE-2018-1099, lets track that here https://github.com/etcd-io/etcd/issues/10479.