Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] [jakarta.ee-spec] Automation for creating boilerplate-spec PRs
I think information that all the spec leads should know should go to the spec leads list, and that's what this seemed like to me.

The public spec committee list is going to be used for ballots.  I guess we should decide what else it should be used for.  Do we  expect all spec project leads to subscribe to it?

David Blevins wrote on 7/11/19 12:39 PM:
It was intended for the public list.  Are we ok to have more discussions there?

My motivation for sending it to that list vs leads is that there is no action item for the leads as I'm not quite done.

Was an update on status of commitments I made to Steering/Spec committees with a slant to be a bit more transparent.


-- 
David Blevins
310-633-3852

On Jul 11, 2019, at 11:11 AM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

David, note that this was sent to the Spec Committee public mailing list.  Was that what you intended?

If you intended it to be public, it probably would've been better sent to the new spec leads mailing list.


David Blevins wrote on 7/11/19 7:28 AM:
End-to-end success achieved on jms-api:

 - https://github.com/eclipse-ee4j/jms-api/pull/225

Generator source is here:


Tried ejb-api and management-api.  Notice some differences that threw the generator off.  Didn't look serious.  Pulled an all-nighter so going to get a few hours of sleep then try on some other projects.

-- 
David Blevins
310-633-3852


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



Back to the top