3 ms·

This comment made/makes me steer away https://github.com/rkt/rkt/issues/3912 https://github.com/rkt/rkt/issues/3912 There is another open issue claiming the p

• ori_b 8y ago
  Why do you believe that churn is a good thing, especially for a thin wrapper around Linux namespaces? There should not be much this is actually doing, so lots of commits would be worrying.
  • edoceo 8y ago
    I didn't say that that churn is a good thing. The github-issue and a sibling are folks asking this question. Why? Lingering bugs? Waiting for features? That the question is open is the concern. And again, compared to my existing tooling which is not having that question and has momentum. Evaluated against docker (a recent move for us) but didn't choose. We also looked a "roll your own" type solutions - required expertise our team didn't have.
• shakna 8y ago
  Last commit 19 days ago. Code commits merged into master seem to be around every 3 months for the last couple years. That seems healthy to me. As for documentation, it seems to have monthly or bimonthly updates. The question in your issue is that their is a lack of activity... Came about three weeks after a commit, and two weeks before another. The issue just seems to be that rkt prefers their mailing list to GitHub issues, though they do pay attention to both. And I don't see a problem with that.