XSF Editor Team - 2020-01-28

clearing the editor queue

Thanks

Sorry I'm not really active lately :x

it’s ok

I have this scheduled window now, which is fine

Yeah but still. It doesn't have to be only you :)

all volunteers

hm

should change of status Draft -> Deprecated cause a version bump, and if it should, in which digit?

hmm.

going with a major version bump, akin to moving to Final

I guess

Which one is that again

Ah the CS

yeah

https://github.com/xsf/xeps/pull/886 Editorial Change && Needs Version Block => Ready to Merge

otherwise I may overlook it

cc @ pep. ^

k

Well Needs Version Block is not ready to merge :p

false

version block is added by the editor

ready to merge is defined as "no acknowledgements needed"

> No acknowledgements of other parties are needed anymore. There may be changes to do at merge time.

Ah, ok then we had diverging definitions :)

the definition is right below the label name ;)

I didn't even know there were descriptions for these

there are more! https://github.com/xsf/xeps/labels

:)

I put some time into writing them some time ago

Yeah.. I never go there

to streamline things

they’re also shown in the dropdown below the names tho

k, well I just type part of the name and <Enter> :x

at least here, maybe that’s just me?

No, not a major version bump, because that explicitly means it's become Final.

https://sotecware.net/images/dont-puush-me/4_DzEj_Ne-G9gUBEITmBdizpYSV746Rih5g8IUaKVk4.png

Kev, aaaagh, I hate our versioning!

I truly hate it

it drives me crazy

Oh, sorry. I didn't mean to be too late.

sure, not your fault

the weird versioning is at fault

either way: what’s the right way then?

I don't know what we've done in the past for this, I'm afraid, but I do remember fairly clearly that bumping major version only happens -> Draft -> Final.

Let's see if Xep1 can help.

Right, XEP-0001 is at least clear that things only become 2.0 if they go Final.

That's something, I guess...

for certain definitions of "clear" ;)

I’ll go with a minor bump then.

Could just do editorial?

On account of there being no change in content?

Kev, I would like to ensure that any notifiable event (i.e. which warrants an email) is at least a minor bump

And if it transpires that it needs to be a minor bump instead, it's much easier to add a bigger bump than it is to undo one?

I won’t be sending mails for purely editorial changes in the future, and I’ll automate that distinction using the version number.

(though, granted, this could also be detected by the change of state)

so you’re right

let’s do this on the patch level…

Kev, thanks for chiming in before I hit the green button :)

Sorry for being a dissenting voice (although I do think it's the right thing to do here).

I haven't found anything in XEP1 yet that helps hint what to do, only what not to do, FWIW. ✏

The last thing to be deprecated was https://xmpp.org/extensions/xep-0137.html in 2018, when Sam used a minor version bump, FWIW.

Prior to that 2017 https://xmpp.org/extensions/xep-0136.html when Sam also used minor. Before that https://xmpp.org/extensions/xep-0130.html in 2012, when Peter did a minor bump.

So if you want to do a minor bump there's certainly plenty of precedent.

(Oh, my ordering is stupid, those aren't the three most recent, but the point probably stands)

I’m going with patch level now

the tooling can deal with that, I was just confused

Anything other than major is probably fine :)