You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.
The releases page describes 0.11.7 as the "latest release," but there are also 0.12.0 and 0.13.0 tags. For the purposes of Homebrew's fleectl formula, which should we be distributing as the current stable version? Right now it's 0.11.7, but I wasn't sure whether that ought to be bumped to 0.13.0 or not yet.
The text was updated successfully, but these errors were encountered:
(I'm not exactly right person to answer such questions, but I just don't want to be unresponsive over a week.)
Short answer is 0.11.7, which is the version installed on CoreOS alpha 1081.
Long answer: I think a particular version of fleet needs to be included in a CoreOS alpha image, to be verified to work in various use cases. As both 0.12 and 0.13 have never been included in CoreOS images, the versions have more steps ahead.
On the other hand, I don't know why even 0.12 is not included in CoreOS alpha. When newer versions could be included in CoreOS images, it would help us find unexpected bugs in advance.
By the way I'm testing fleet 0.13 (and newer) nearly every day, and I've tested it also with CoreOS alpha 1081. So far it seems to work fine. No error.
@aneeth PR #1291 (for issue #1290) is not merged yet, and not available yet in 0.12 or 0.13. I reimplemented the same one as #1510 , which is still pending. More reviews are welcome.
I suppose #1456 is also about the same issue.
The releases page describes 0.11.7 as the "latest release," but there are also 0.12.0 and 0.13.0 tags. For the purposes of Homebrew's fleectl formula, which should we be distributing as the current stable version? Right now it's 0.11.7, but I wasn't sure whether that ought to be bumped to 0.13.0 or not yet.
The text was updated successfully, but these errors were encountered: