Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] [EXTERNAL] Re: Release plan revisions to mitigate impact of gh-platform-820 and preserve June/July delivery of EE 11
  • From: Ed Burns <Edward.Burns@xxxxxxxxxxxxx>
  • Date: Tue, 16 Jan 2024 17:19:21 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=5J7BRN9j7tjhRDUSvPN04KG9owWDXKrUgM4aEX7lx34=; b=lURgCTds28CFgZNeUkDNRnuzfYoMckgMGeaKutx8cR7xFmEvLWNYwgBJVWpzMleIDM0kQ+G1fGZrF96osboUlCzX8RXrdsmMemmSU4NlJy62j/ZcjTbjnmDJBCDlPWm+2htuMv9hCCEaEc4Y9YYOvz3MUsWS/wCacXyBV3yB5glnIBij+VSvxhxHTrE2tVIqjy26W682X3DHDm+XkB0CVR13JBflp/yr0gQoImGjGuKjonise4d++H9pG0sG6ovJflL1WFHx41ZxzU9IIE4Ylf26pb9HYi3frbjgyP83xmA4rJQieErLEMXQKcY5j6D5gEAVZusE7JjMG1WIezaQYQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TvKmYlyBRrFanXD5916HLzu4mifJPpWw6lg8TGgCxDrCUvFcQB46NOxroAtQ2tqY3Vwo0iX6+7lFP9xR6efgK+jpAgFCnxTCDfnWW/M5w+TOIJxpKRoJpot7aKcrkrynBMLMp8qdZTAEWNSUVegnvTomtM1/duZa1yA1oBYV1s+cz0uMpID0IS8Gc/r/0vNnwJIYJwUuXONsBNxcGmz2vKLblzQAAlgugEa+fiYmmXyVljT6VcPF1mOkhlr/Od99bdewDQks5KCh6sqgGmNUd3kaTO87+SU7+qgojE9Js4mFqMKNdpjugGYf/rnwiOxGPBUQaazo3UIcm7jtVIgwrQ==
  • Delivered-to: jakartaee-platform-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/jakartaee-platform-dev/>
  • List-help: <mailto:jakartaee-platform-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev>, <mailto:jakartaee-platform-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/jakartaee-platform-dev>, <mailto:jakartaee-platform-dev-request@eclipse.org?subject=unsubscribe>
  • Msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2024-01-16T17:01:44.2026475Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard
  • Thread-index: AQHaSGe7/C1T2TS9pkeAT/WhHZ0gWLDcfd1ggAAcGACAABCZ8Q==
  • Thread-topic: [jakartaee-platform-dev] [EXTERNAL] Re: Release plan revisions to mitigate impact of gh-platform-820 and preserve June/July delivery of EE 11

Mark Thomas wrote:

 

MT> Compare that to:

MT> Jakarta EE 11
MT>   - Minimum Java version 21
MT>   - TCK tested with Java 17 and Java 21

 

Thanks for clarifying. The text iterating has now moved into PR 822 to modify the EE 11 Release Plan.  Here is the permalink to the line in the Release Plan addressing the central point, current as of this writing.

 

Steve Millidge wrote:

 

SM> I am confused as to why it is necessary to switch direction at this late stage and why this decision is being made in the platform project.

SM> The reason stated in the GitHub issue is about market adoption so I think the steering committee should be brought into the loop to provide a steer.

SM> The working group side of Jakarta EE is where market adoption concerns should be resolved.

In my capacity as release co-coordinator, I agree with your observation that the steering committee is the appropriate place for market adoption related issues.

 

Further, I observe that the outcome of the platform project adapting to the request in gh-platform-820 is the platform project’s continued implementation of the steering committee’s suggestion to “target Java 21”.

 

In other words, the steering committee told the platform project, “EE 11 should target Java 21”.  Our response to gh-platform-820 is how we are doing that.


SM> I am assuming there is no technical reason why JDK 21 can't be the baseline as the given amendment to the release plan states that there will still be a

SM> shippable runtime running on JDK 21 therefore all Compatible Implementations must support Java 21? 

In my capacity as release co-coordinator, I want to have the maximum number of certified compatible implementations. Our response to gh-platform-820 is how we are doing that.


SM> Actually having to support JDK 17 and JDK 21 in the TCKs and GlassFish project I assume is a lot of additional busy work. 

 

Yes, it is a whole lot of busy work. This why I stated this expectation earlier in the thread:

 

EB> The key condition to make this plan possible: the GlassFish community is willing and able to deliver an implementation of EE 11 compiled under 17,

EB> but passing the platform TCK under 17 and also 21. The release coordinators expect more community involvement on the Jakarta Data implementation for

EB> GlassFish, especially from Red Hat, to achieve this goal.

 

Thanks,

 

Ed

 

 

| edburns@xxxxxxxxxxxxx | office: +1 954 727 1095

| Calendar Booking: https://aka.ms/meetedburns

|

| Please don't feel obliged to read or reply to this e-mail outside

| of your normal working hours.

|

| Reply anonymously to this email: https://purl.oclc.org/NET/edburns/contact

 

Back to the top