> > > > Saying that I think it would be good to have a deadline or a list > > of people we want comments from. Mark, Simon, Ludwig, Viktor, > > yourself and myself come to mind … we need to know what our > > approach is, and this ties back to the “feature gating” discussion > > that I hope you saw. We need a way to have features we are working > > on, so we can test and reason about them, but without letting them > > out in production - and having ways to roll the back. > > Coming in late to the discussion... So, in this case with > nunc-stans(the new PR) I think we should do some basic sanity tests > on > it (which are occurring right now, and one issue was found which you > are > already aware of). Once these basic sanity tests pass then we > should > merge it. After that we can do the more extensive testing on it > from > master branch, but I don't want to commit something that is > completely > broken (even though the current state of NS isn't great). Anyway, I > think that's a fair compromise :-) I agree - now lets hope that I can find a solid few days to work on this so I can give the tests and debugging the attention it deserves ... :| _______________________________________________ 389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-devel@xxxxxxxxxxxxxxxxxxxxxxx
