Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec] Question on plans for Batch Service Release
  • From: Thomas Watson <tjwatson@xxxxxxxxxx>
  • Date: Wed, 3 Apr 2024 16:56:56 +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=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=34IIqn0hzMIVqiBmVxBQRARx6fSON9Zep04M4d2qpBs=; b=Jo9pFscoU6Nnre8VXAHNe51VAVnix7exoZJp8it4hj0MxaEtvtYbgNH8quBcmwapLG6wSqgsEL7yWHDqkLpI1Y6m6P00QQK5To6dM9FDboG0/SdbOKZ+GwBqX+e87/8+GnVgnEoU8hbSuGTk9swnDD54SzbEFsNiSSHIEVRByZ+NLWON39e7BhR+tEl3CCsyUeQFHZMWxDBp2XPpfPodvFsP9W81vYpk7JFb3O8OYCaQBDa4E+IpLSO+Ncg5ZIH4Z9O6Wja5qGe+KVmoEnDU0rsRlRJ0RYIq/HTmXzIxk80kZ5PkoEqVEYr3YVJTXqVbakGoUVwZAixYx9t/EPB8zQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=XJwXSJB4zBQ8qCvM9NztXky4+NaA0ABMT+RdKnKo2WiYRrW6mlXLDQhfs0NZZc/lOHo9CscY5x8Wmt5PMayFVvmgmzAgKqEEsExIoZf+kZHixHzxk9OZ03Q7PFn40NIHVxb+jDS3w9LwbKOY/4/WOCO3HAUN1Z3KDxSE1zboKXAkveU5DjV59Its5egu9f5yg3V6uc8SiuJFwkH6WqAMouum4J2JK02bakJwM9mwm+2AUqaczFd+em9J+MFh75cvL4DXfIl0gF/lAUUOJmhafH6+kxTH8S2Q6vO9/U3aAjcCFmjMs4Uz79kx/31OVwn16GzgFPG9ykQDXA42AwsxUA==
  • Delivered-to: jakarta.ee-spec@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/jakarta.ee-spec/>
  • List-help: <mailto:jakarta.ee-spec-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec>, <mailto:jakarta.ee-spec-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/jakarta.ee-spec>, <mailto:jakarta.ee-spec-request@eclipse.org?subject=unsubscribe>
  • Msip_labels:
  • Thread-index: AQHagcv6U0N4ObXQZE6kwEGJI6gzwrFWypGW
  • Thread-topic: Question on plans for Batch Service Release
Hi Scott,

This was discussed on the Platform call and then also brought up on the specification committee call.  The specification committee proposes a service release of the TCK be done to address the challenge.  Then, at a later time, do an update of the spececification in the next minor or major release to the spec. In this situation the TCK would, for a period of time, be out of sync with the specification. The committee accepts this proposal provided an issue to be opened to track the future update the Batch specification.

Thanks
Tom Watson

From: jakarta.ee-spec <jakarta.ee-spec-bounces@xxxxxxxxxxx> on behalf of Scott Kurz via jakarta.ee-spec <jakarta.ee-spec@xxxxxxxxxxx>
Sent: Friday, March 29, 2024 6:53 AM
To: Jakarta specification discussions <jakarta.ee-spec@xxxxxxxxxxx>
Cc: Scott Kurz <skurz@xxxxxxxxxx>
Subject: [EXTERNAL] [jakarta.ee-spec] Question on plans for Batch Service Release
 
Hello, I would like to review my plans for a Service Release for Jakarta Batch. Though a lot of the process is well-documented, I'm double-checking because I plan to update the spec document as well for a TCK challenge. For this challenge,
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd
Hello,

I would like to review my plans for a Service Release for Jakarta Batch.  

Though a lot of the process is well-documented, I'm double-checking because I plan to update the spec document as well for a TCK challenge.

For this challenge, while we will exclude the relevant test, this doesn't seem sufficient, since the test is backed by clear text in the spec doc.
After discussing with some CDI folks, though, it seems we went too far and need to remove this language (and hopefully clarify in future releases)   

I have a PR up for review to update the spec doc language: https://github.com/jakartaee/batch/pull/211

One reason in particular I'm asking is because the SR PR template:  https://github.com/jakartaee/specifications/blob/master/service_release_pr_template.md text includes this:

>  Note: Specifications themselves do not have service releases. Only the associated API (limited to JavaDoc updates), JavaDoc, and TCK artifacts can have service releases....

Is that intended to exclude the possibility of updating the specification doc in a service release?  Or is it more just emphasizing that the Specification as a whole remains at the same 2.1 level regardless of service release, e.g. in the view here: https://jakarta.ee/specifications/batch/ and in the way the https://github.com/jakartaee/specifications   repo is organized?   Perhaps this type of case just isn't common.

---

In addition, the Service Release will also update the TCK to support validation with Java 21 (for EE 11).  I don't have any questions around that, just mentioning for completeness.

Thank you,
Scott 

Back to the top