Skip to content

Conversation

amitkumarj441
Copy link

@amitkumarj441 amitkumarj441 commented Jul 4, 2017

Signed-off-by : Amit Kumar Jaiswal [email protected]

@richm
Copy link
Contributor

richm commented Jul 5, 2017

Unfortunately we can't yet move to fluentd 0.14. Hopefully in the next major (3.7) release.

@amitkumarj441
Copy link
Author

amitkumarj441 commented Jul 5, 2017

@richm Sure! Thanks for letting me know about this info.

@openshift-bot
Copy link

Origin Aggregated Logging Action Required: Pull request cannot be automatically merged, please rebase your branch from latest HEAD and push again

@openshift-bot openshift-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 14, 2017
@portante
Copy link
Contributor

Also, according to http://www.fluentd.org/download, 0.12 is considered "stable" and ready for production use. When 0.14 moves to that, we should consider it then.

@cosmo0920
Copy link

Now, Fluentd v1 , which is just bumped up version from v0.14, became stable release and v0.12 became old stable.

@richm
Copy link
Contributor

richm commented Jun 20, 2018

maybe when rhel8/centos8 is available we can switch - but for now, we're stuck on ruby 2.0 :-(

@richm richm closed this Jun 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/fluentd DO NOT MERGE !! needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. release/3.7
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants