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
l've looked into this a little bit when starting the review of Lars' PR for the zookeeper operator, as I stumbled across his use of the nightly toolchain right of the bat.
The general consensus seems to be that nightly is fairly stable and people do use it in production, as anything that goes in it is extensively tested. Anything that breaks prior working things do not go into master/main. But of course no one will ever straight up say "yes it is stable enough for production".
However this does not mean that stuff might change abruptly in nightly, so if we always use the latest available nightly version we run the risk of a build working one day and failing the next (not a huge risk, but a possibility).
The big issue in our case is the backtrace feature, which is not in stable yet - if we want that we need to run nightly.
Maybe as a compromise we can agree to use a fixed version of nightly for our builds and update that every few weeks or so. That way at least it will be a conscious decision to upgrade and we know to watch the next builds closely.
I'd still prefer if we moved to stable at some point though.
No description provided.
The text was updated successfully, but these errors were encountered: