Lines Matching full:protocol

4 available in the Wayland core protocol. Such protocols either add
6 protocol either in Wayland core, or some other protocol in
9 A protocol in wayland-protocols consists of a directory containing a set
10 of XML files containing the protocol specification, and a README file
13 ## Protocol phases
18 In the development phase, a protocol is not officially part of
28 the protocol can still change.
30 When a protocol has reached a stage where it is ready for wider adoption,
33 met, it enters the "testing" phase. At this point, the protocol is added
40 replaced with a new major version, or a different protocol extension all
43 After a staging protocol has been sufficiently tested in the wild and
50 A protocol may be deprecated, if it has been replaced by some other
51 protocol, or declared undesirable for some other reason. No more changes
52 will be made to a deprecated protocol.
54 ## Legacy protocol phases
56 An "unstable" protocol refers to a protocol categorization policy
61 During this phase, protocol extension interface names were in addition to
65 ## Protocol directory tree structure
67 Depending on which stage a protocol is in, the protocol is placed within
73 Unstable protocols (see [Legacy protocol phases](#legacy-protocol-phases))
77 ## Protocol development procedure
79 To propose a new protocol, create a GitLab merge request adding the
86 If the new protocol is just an idea, open an issue on the GitLab issue
87 tracker. If the protocol isn't ready for complete review yet and is an
101 the protocol interface names in order to minimize risk that the generated
107 should be used on all interfaces in the protocol.
117 ](GOVERNANCE.md#21-protocol-namespaces).
119 Each new protocol XML file must include a major version postfix, starting
122 protocol.
124 The interfaces in the protocol XML file should as well have the same
127 For example, the protocol `foo-bar` may have a XML file
138 Warning! The protocol described in this file is currently in the testing
144 ## Backward compatible protocol changes
146 A protocol may receive backward compatible additions and changes. This
150 ## Backward incompatible protocol changes
152 While not preferred, a protocol may at any stage, especially during the
160 - Increase the major version number in the protocol XML by 1.
167 ## Declaring a protocol stable
169 Once it has been concluded that a protocol been proven adequate in
176   same name as the protocol directory in the `staging/` directory.
179   should be the same name as the protocol directory but with the `.xml`
181 - Remove the disclaimer about the protocol being in the testing phase.
184 - Replace the disclaimer in the protocol files left in the staging/
188 Disclaimer: This protocol extension has been marked stable. This copy is
193 Note that the major version of the stable protocol extension, as well as
196 There are other requirements for declaring a protocol stable, see
211 ~"New Protocol" - For a new protocol being added. If it's an amendment to
212 an existing protocol, apply the label of the corresponding protocol
215 ~"Needs acks" - If the protocol needs one or more acknowledgements.
218 protocol.
220 ~"Needs review" - If the protocol is in need of review.
222 ~"In 30 day discussion period" - If the protocol needs a 30 day discussion