[Council] Advancing more XEPs to Final
chris.mullins at coversant.net
Fri Dec 1 13:22:56 CST 2006
I'm happy to propose and accept a definition like that.
The thing that I don't like is the huge number of "stable" XEP's that we
have (and depend on) that are not in a state that reflects this.
It's hard for me to get in front of a group and evangelize features like
MUC, and when asked, "What status is that standard in?" to reply with
From: council-bounces at jabber.org [mailto:council-bounces at jabber.org] On
Behalf Of Ian Paterson
Sent: Friday, December 01, 2006 11:02 AM
To: XMPP Council discussion list
Subject: Re: [Council] Advancing more XEPs to Final
Chris Mullins wrote:
> I was looking at the (very short) list of standards-track XEPS that
> are in final status, and thought it's time to perhaps advance a few
IMHO that depends on what Final means. Putting to one side for a moment
what it means within the XSF today, I'd like Final to mean "no backwards
incompatible changes will be introduced" (and perhaps even that "the
schema MAY be extended"). Not final in the sense that there would be
absolutely no material changes (only clarifications).
If Final means the later, then I'd like us to introduce a new category
between Draft and Final with the meaning of the former ("no backwards
incompatible changes will be introduced"). IMHO it seems like a very big
jump from Draft (which allows backwards incompatible changes) to Final
(assuming it allows no changes at all).
The name of this category should sound relatively final (for sales and
marketing purposes). e.g. "Complete" or "Finished"
More information about the Council