Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [glassfish-dev] About CCR for maintenance release
  • From: "sawamura.hiroki@xxxxxxxxxxx" <sawamura.hiroki@xxxxxxxxxxx>
  • Date: Fri, 25 Feb 2022 07:42:24 +0000
  • Accept-language: ja-JP, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=fujitsu.com; dmarc=pass action=none header.from=fujitsu.com; dkim=pass header.d=fujitsu.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=SepLGrLD5hJadBtw+6FCX7owv7+xwCzZUTjs6k/q+1k=; b=Eoca6dkX2v1vN7QPgQtcjqP6XMJSBhNqs99Tp6Gl1BHEjU2zAlBZNHHZ0h99LO2+O5GMhW7B4t9ONUbv0LqDtDgHXORLuZyxuAjWA2Vs5PyV7X7g7nuCx/yOgTgX+SiOOZZBjzV28evK4SK9EhvxbuhTh8BuCPjJWofZLMJAJl6xNJD3W7S3dVU6kD/H5WvUZYrbByXTAtW1pUap9mtvsNg3RQZYfqbbB2th/E+1TLgrOYb+qoC343rLGnAUWQuLbD1f2SWvUjA3+R2TKGJT3xkyk0/dNXhs5CidGvr2gwIvR6n7NHjPl8BTd7oCkDgUqlA3yDTN/gGerAeC3X30yw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nsTHcVJEyw4PpULnnsdTvfd9k/Vy+tK1p9JcZxXfri9vO7JRRdfNWeAIFOZ3+wua/+itvvY/cS+xd5Nn4ZhD8IDX1oPc/upn4VNp5GqFVA42MBZXVOMFV3qwxGyXtk9pZKlPH4aANiat2XjuCflE9uyTSBAtiZlyJQeVmkUCHItJMlaf8jexCUi2cit3UGj3aRyPFAxNoiI0Xza+ytyR0XDOqy9eO3eD/Txlf2t/HmBP3hT3gBf3+vGbZZKJmoLa3GAG9LTzN8F2UE79zoqwqaHen5+/GmFgY/2Nt71vts1wzS2Nvf1ULnHUGZPSOyfj2LAD8Iy6rBdAoR9egcXnVw==
  • Delivered-to: glassfish-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/glassfish-dev/>
  • List-help: <mailto:glassfish-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/glassfish-dev>, <mailto:glassfish-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/glassfish-dev>, <mailto:glassfish-dev-request@eclipse.org?subject=unsubscribe>
  • Msip_labels: MSIP_Label_a7295cc1-d279-42ac-ab4d-3b0f4fece050_ActionId=aeef9276-1fbc-47b7-ad20-a433a6db0abc;MSIP_Label_a7295cc1-d279-42ac-ab4d-3b0f4fece050_ContentBits=0;MSIP_Label_a7295cc1-d279-42ac-ab4d-3b0f4fece050_Enabled=true;MSIP_Label_a7295cc1-d279-42ac-ab4d-3b0f4fece050_Method=Standard;MSIP_Label_a7295cc1-d279-42ac-ab4d-3b0f4fece050_Name=FUJITSU-RESTRICTED￢ﾀﾋ;MSIP_Label_a7295cc1-d279-42ac-ab4d-3b0f4fece050_SetDate=2022-02-25T06:59:44Z;MSIP_Label_a7295cc1-d279-42ac-ab4d-3b0f4fece050_SiteId=a19f121d-81e1-4858-a9d8-736e267fd4c7;
  • Thread-index: AdgpWlm626zvyOe4SjyyBhSbqHgeugAJBBeAAAhY1IAAHV3K0A==
  • Thread-topic: [glassfish-dev] About CCR for maintenance release

Hi,

 

I think we don't need to issue the CCR for the release still in development.

However, for the final release, I feel like we need to issue the CCR to release GlassFish as "Jakarta EE compatible implementation" even with a minor updates.

 

On the other hand, It will take about two weeks for the CCR to be approved. so it may not be appropriate to issue it every patch release.

 

I'll check the CCR description again and if there are no clear rules, I will ask the jakartaee-platform.

 

Kind regards,

Hiroki

 

From: glassfish-dev <glassfish-dev-bounces@xxxxxxxxxxx> On Behalf Of Scott Marlow
Sent: Friday, February 25, 2022 1:59 AM
To: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>; arjan tijms <arjan.tijms@xxxxxxxxx>
Subject: Re: [glassfish-dev] About CCR for maintenance release

 

On 2/24/22 7:59 AM, arjan tijms wrote:

Hi,

 

Good question. I've made sure that each and every release passes the EFTL certification and certification-web. See the jobs here: https://ci.eclipse.org/jakartaee-tck/view/EFTL-CERTIFICATION-JOBS/

 

As we're on a monthly cadence, should we add a job to issue the CCR as part of the release process?

Perhaps we should discuss if there should be CCR for all releases (alpha, beta, CR, final perhaps) on one of the Jakarta Platform or SPEC mailing lists.

Each CCR has to be reviewed, I am concerned with there being too many CCRs to review if implementations have to submit new CCRs even though they haven't changed to new EE SPEC API versions.

In the mean time would it be enough for the CI job to just post the TCK results on https://glassfish.org/certifications/jakarta-platform as part of self validation?

Scott

 

Kind regards,

Arjan Tijms

 

 

 

 

 

On Thu, Feb 24, 2022 at 10:09 AM sawamura.hiroki@xxxxxxxxxxx <sawamura.hiroki@xxxxxxxxxxx> wrote:

Hi,

I have a little concern about maintenance release.
Since we issued the GlassFish 6.1 CCR last year[*1], we have published several maintenance releases[*2], do these not need the CCR?
[*1] https://github.com/eclipse-ee4j/jakartaee-platform/issues?q=is%3Aissue+GlassFish+is%3Aclosed+label%3Acertification
[*2] https://glassfish.org/

Kind regards,
Hiroki
_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev



_______________________________________________
glassfish-dev mailing list
glassfish-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/glassfish-dev

Back to the top