Hi folks, As we are just about to tag 1.3-rel RC5, I suggest that ONLY patches that fix certification-blocking issues be merged between now and when we have a 1.3.1 final tag done. I've given a -2 review to many patches that look perfectly fine, along with a comment that I'll remove the -2 as soon as RC5 is done (but I guess I meant to say, as soon as 1.3.1 is tagged).
Even very safe changes create a bit of instability and extra work, as all the devs and QA working on finalizing the release have to re-fetch and re-pull and re-build 1.3-rel. Since we are already a few weeks behind schedule for 1.3.1 release, I hope everyone can hang on just a bit before we merge anything more to 1.3-rel. There is a follow-on release planned immediately after 1.3.1, in order to incorporate other very important features, so these patches can go into that release (1.3.2?), too, before we move off of 1.3-rel and onto master for the next major version. Obviously this isn't my sole judgement call (it's probably Uze's or Abitha's) but I'm suggesting this and hope we can agree. Thanks, Nathan
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
