On 13 Jan 2019, at 11:29, Jonas Schäfer <[email protected]> wrote: > > On Dienstag, 25. Dezember 2018 17:43:28 CET Kevin Smith wrote: >>> On 20 Dec 2018, at 20:27, Tedd Sterr <[email protected]> wrote: >>> Dave noticed that Jonas pushed through XEP-0412 (XMPP Compliance Suites >>> 2019) before all votes have been made, and has literally no idea what do >>> to about it as there is no process to handle a process violation. Jonas >>> suggests reverting the changes in Git; Georg suggests pretending it never >>> happened unless the final vote contradicts, and revert if so. Dave thinks >>> reverting would be a bad idea as it could lead to 0412 referring to a >>> different XEP. >> I don’t really want to be the blocker of progress, but there are various >> things in here that I’m not convinced by. > > Sorry for putting the pressure on you by delaying the suites for such long > time, even though I did not intend to do so. > >> Some of them (368) were existing >> things that I don’t feel are really essential in a core client/server > > Noted and fixed. > >> , or >> are inconsistent (84 but not 163 in a server), > > Noted and fixed. > >> others are new (what does it >> mean for 184 to be supported by a server? > > That was simply a typo, thanks for pointing it out. > >> 398 is neat, but does it deserve >> to be in a compliance suite already?). > > Yes, I think so. It provides valuable support in moving the ecosystem forward. > >> I’m also not sure that 7622 is >> actually practically required for interop, as opposed to 6122, and a note >> to that effect would be sane. > > Changed. > > (The actual change isn’t published yet, but it only hinges on the docker > build.)
Thanks. +1 based on the changes described above. /K _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
