Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-community] [jakartaee-spec-project-leads] Community Retrospective on Jakarta EE 8 Release

David,

I don't have write or comment permission on that document, so I'll give you my feedback here.

From the Servlet Spec point of view, the process felt very chaotic and out of control.   There are too many committers on the project, some of whom appear to either have more experience with the process, inner workings and/or out of band information.   The two spec leads felt very out of control as PRs were often submitted by one committee, reviewed by another and then merged in short order without any opportunity for wider discussion or review.  The same happened with releases candidates that were built and promoted also without any input from the spec leads!

All this was done in good faith by well meaning individuals, who for the most part did the right thing.... but that approach does not encourage community, communication, consensus.     I know everything was a bit rushed and having busy spec leads being swamped by process probably was a bit of a hand brake.  But if the spec leads don't know what should be done, educating them is better than bypassing them.   I'm not saying that the spec leads opinions are the only one that count, but they should be responsible for communicating to the expert group and getting a rough consensus.

For this release, it didn't really matter that much because we were not changing anything technical.  But I fear that if the same is repeated for the next iteration, then the chaos is likely to be damaging to quality and consensus.  I would very much like to see a change in process where only spec leads can merge PRs or promote releases.

cheers



On Wed, 9 Oct 2019 at 13:18, David Blevins <dblevins@xxxxxxxxxxxxx> wrote:
The Jakarta EE Steering Committee has begun the process of doing a retrospective on the Jakarta EE 8 release and would like to open feedback to everyone to do the same.  We would like to hear from everyone; contributors to specifications, implementers of specifications, users of specifications and those observing from the outside.

The goal is to collect feedback on the Jakarta EE 8 delivery that can be turned into action items to improve our delivery of subsequent releases, enabling as much of the community as possible.

This is not a technical roadmap discussion.  Please deliver that feedback directly to the specification project.  Feedback here should be applicable to any future Jakarta EE release.

• https://docs.google.com/document/d/1E7uHGyvjDH0fimxxdHwHtC6iZIC9wwEBfWLRilVQs80/edit

Write your feedback in the above Google doc.  When providing feedback we ask:

• Be succinct.  A sentence or two per point.  Use the list for greater detail if needed.
• Be constructive.  If something didn’t work, what should we do next time?
• Be you. Please put your name on your feedback.  We value your contribution and ideas

We would like to leave this document open for 10 days.  Please have your feedback in by October 19th so we can include it in any final retrospective actions.

_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads


--

Back to the top