mdoschhttps://github.com/xsf/xeps/pull/996/ should be splitted as it touches several XEPs and revision blocks should be added right?
mdoschAlso does https://github.com/xsf/xeps/blob/master/docs/TRIAGING.md No 5 apply to all XEPs not being ProtoXEPs and not in experimental state? So also for deferred XEPs?
jonas’mdosch, #996 touches a bunch of related XEPs and it may be purely editorial
jonas’in which case it might be OK to not split it, but it does need the [Needs Revision Block] label
jonas’in which case it might be OK to not split it, but it does need the [Needs Version Block] label
jonas’mdosch, good catch w.r.t. Deferred; if you have the time, please make a PR against TRIAGING.md to fix that. Deferred should be treated the same as Experimental, except that a note needs to be added for the Processing Editor to remind them of de-Defer the XEP if the changes are non-Editorial
mdoschVersion not revision block label?
mdoschAh I see. Thanks :)
jonas’the label is called Needs Version Block
jonas’there is no Needs Revision Block label
mdoschYes, I saw just after I asked. :D
mdoschAnother thing: For the "flow chart" in 3 ii and iii should have an stop added and should be moved before i. Otherwise you'd add the label ready to merge prior to checking for the version block.
jonas’that is OK
jonas’or maybe not, the order could be flipped
jonas’Ready to Merge and Needs Version Block are not mutually exclusive
jonas’Ready to Merge just means that the author does not need to do anything and that all approvals have been collected
mdoschWouldn't you wait for the change before merging?
jonas’only if you let the author do it
jonas’Needs Version Block is mainly an instruction for the Processing Editor, not for the author
mdoschDe-deferr means changing the state to experimental?
mdoschI wanted to push it to my fork and PR but I accidentally pushed directly to the repo. :(