Because SHOULD opens much room for interpretation, while according to the EDP the committers are personally responsible that everything is in order. So we committers need to know what in order means, which has no room for interpretation. Either we commit it or not. Either it is in order or not. So something MUST be that way, or not.
-Markus
From: jakarta.ee-community-bounces@xxxxxxxxxxx [mailto:jakarta.ee-community-bounces@xxxxxxxxxxx] On Behalf Of Mike Milinkovich
Sent: Donnerstag, 13. September 2018 15:49
To: jakarta.ee-community@xxxxxxxxxxx
Subject: Re: [jakarta.ee-community] JAX-RS 2.1.1 Available On Maven Central
On 2018-09-12 5:39 PM, Markus KARG wrote:
Mike told us that the feature has to be proven its use in a product.
I get the impression that everything I say is automatically interpreted as a MUST when what I am trying to (almost always) say is SHOULD.
The Spec Process is going to say that a Specification Version MUST have a least one open source implementation released before the spec can be adopted as final. Everything else is a SHOULD.
![Avast logo]()
| This email has been checked for viruses by Avast antivirus software.
www.avast.com |
