Re: Restore write access for all EG members?
toggle quoted messageShow quoted text
What can I say? It would have been just as easy to announce to the group that the repo was effectively locked until further notice while preparing the PRD. You can additionally always take a note of the revision number to see what the exact version for the PRD is, or create a tag even.
That's exactly what Ed Burns and Manfred Riem did for JSF and everyone kept to that. Actually revoking the access, well intended or not, is IMHO not the right way to go forward with this.
It may be work to revert, but it's also work to let you be the bottleneck. As for the cost, it's generally known that an optimistic lock is cheaper than a pessimistic lock. Assuming that there's surely going to be reverting done is a pessimistic lock, and I'm sure you didn't intent it to be but almost by definition a pessimistic lock comes across as, well, pessimistic.
There's an amount of mundane work to be done, like moving things to the agreed javax.security.enterprise package. The PR for that can be immediately approved after quick review by basically any experienced EG member. This also makes it much easier to start the next PR right away and minimises the chances of merge conflicts.
The suite of tests is in the /test folder here https://github.com/javaee-security-spec/soteria/tree/master/test
I run them prior to every change and commit, and since I'm only human I could of course make a mistake and run them against the wrong version or something like that, so there's a CI job as well that also runs the entire test suite.
On Wed, May 31, 2017 at 10:54 PM, Will Hopkins <will.hopkins@...> wrote: