Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cu-dev] New release for Jakarta EE 12?
  • From: Nathan Rauh <nathan.rauh@xxxxxxxxxx>
  • Date: Mon, 17 Mar 2025 20:09:58 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=us.ibm.com; dmarc=pass action=none header.from=us.ibm.com; dkim=pass header.d=us.ibm.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector10001; 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=/9+g8QxCHUQuDIRVP70v02JuoqpL1YUzMTsw6hIdbr4=; b=wEyiyy1s4W/B+Mw4en1/410lfbTAIsfko4XWs4w5BN9P94FdC5zPF+LJ28PN0npTYS4v+Uy/gDdfRfUUcZa8n35fMzYaOtk0cd9UgyYGFc1qQSP0pcH3+JDZ1FDtUOwdm+be4POCRwebdZJMCjY3HLnBmrv8PSHCoZuRWZSSpL8Yy129ZOao/llMJGGZrSkMR02wTPb9thZoRu7tgIFbodzVpo2BT91o9Wg4CPSGHNuRriJRK2TV1gmKReyJncfRvA5Xwt5NYBehr3ytRZ4fDrFjVzUgjiaYd5WpPBsCbpu+AXb8fHU5sclg+cmO0sGiUa2FowW9vHDODWewdu67+g==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector10001; d=microsoft.com; cv=none; b=StgALQDHEdD680pizzlzTaDEcfmL2qKlTz821dSUZAwjTT0Fs66P8F+7q/d+fBKvsDdtcNzWyO8fYE4ZylOB9Qxv4rWbr7KgPrAaWQIVVQTay1oYuJ4yd034GUE7zD64Vxlcx/9b/+32qL91CpaEk4UDIeY9dogY/eMeFWFWnIWdSUPC2yi0GK/F+BmXLDciz7CqhGk3H5SOs5wgpp5VsGHjCNYamkC9fycEHoZpryTPPMs96O2MPJx+NX9FhQqZfOKWQ4hCD4/VS8rslAl2DUkAQDSbd7f3v5p9M0H7q3HqNkLRRDOKpKKlnai0+jjBK1iWVa9O148cCOAUk0y+tg==
  • Delivered-to: cu-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/cu-dev/>
  • List-help: <mailto:cu-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/cu-dev>, <mailto:cu-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/cu-dev>, <mailto:cu-dev-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AQHbiIyuTI0nyyXcREmglQOjobHagbNdPQN7gBqhf6c=
  • Thread-topic: New release for Jakarta EE 12?

Based on the proposed content in the 3.2 milestone, I put together a draft release plan for Concurrency 3.2:

https://projects.eclipse.org/projects/ee4j.cu/releases/3.2/plan

 

I’ll leave it in draft state for the next week for any discussion that might come up, and if there are no objections or concerns after that, I’ll go ahead and submit it as the release plan.

 

 

From: cu-dev <cu-dev-bounces@xxxxxxxxxxx> on behalf of Nathan Rauh via cu-dev <cu-dev@xxxxxxxxxxx>
Date: Friday, February 28, 2025 at 3:29 PM
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Cc: Nathan Rauh <nathan.rauh@xxxxxxxxxx>
Subject: [EXTERNAL] Re: [cu-dev] New release for Jakarta EE 12?

The Concurrency git project has a 3. 2 milestone that we can use as a starting point. I would suggest that we take the next several weeks to figure out what we want there and use the outcome of that as a guide to create the plan. From: cu-dev

The Concurrency git project has a 3.2 milestone that we can use as a starting point.  I would suggest that we take the next several weeks to figure out what we want there and use the outcome of that as a guide to create the plan.

 

From: cu-dev <cu-dev-bounces@xxxxxxxxxxx> on behalf of Jared Anderson via cu-dev <cu-dev@xxxxxxxxxxx>
Date: Wednesday, February 26, 2025 at 3:51 PM
To: cu-dev@xxxxxxxxxxx <cu-dev@xxxxxxxxxxx>, Edward Burns <Edward.Burns@xxxxxxxxxxxxx>
Cc: Jared Anderson <jhanders@xxxxxxxxxx>
Subject: [EXTERNAL] [cu-dev] New release for Jakarta EE 12?

Community members, Executive Summary 1. See issue #671. a. If you don't plan to have a new version for your specification in EE 12, just close the issue. b. If you plan to have a new version, use the issue to create a release plan by April 15,

Community members,

 

Executive Summary

 

1. See issue #671.

      a. If you don't plan to have a new version for your specification in EE 12, just close the issue.

      b. If you plan to have a new version, use the issue to create a release plan by April 15, 2025.

2. See this dashboard where the component release plan issues are tracked.

 

 

Details

 

On Monday I opened issue #671 in your repository to request your community to consider a new release of your component for Jakarta EE 12 by creating a new release plan.  The issue contains a lot of details that explain what to do to create a release plan.   You can use the issue to document initial thoughts and reference other issues in your repository as you work out what you want to include in a release plan.  

 

A dashboard in GitHub was created to track the status of the release plan issues.  The dashboard, located here, contains both a Board and Table view of the release plan issues.  What is being asked of each community is to decide on if you plan to have a new release to be considered for EE 12 or not.  If not, closing the issue will move it to the final column on the dashboard.  If you are planning to have a new version of your component for EE 12, please follow the instructions in the issue by April 15, 2025 in order to get your issue moved to the second column for your mentor to look at the issue and get it ready for a plan ballot.  You will see that your issue in the board includes the name of the mentor that was assigned to your component in EE 11.

 

Thanks,

 

Jared Anderson and Ed Burns

Jakarta EE 12 Release Co-coordinators

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Back to the top