Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cu-dev] Please confirm: no Incompatibilities for Concurrency 3.0?
  • From: "Steve Millidge (Payara)" <steve.millidge@xxxxxxxxxxx>
  • Date: Sat, 17 Sep 2022 07:46:35 +0000
  • Accept-language: en-GB, en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=payara.fish; dmarc=pass action=none header.from=payara.fish; dkim=pass header.d=payara.fish; 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=d2lWLmNXMxE/j6i7hShbUqHJR6fUrxEWEpcshLLhWXE=; b=mDvWcqHXlvHreHzhOBHlO8FMqM4kk8wR++dvyGwstUbo7hdty2SH6B6zpbocWfqBogTBmqUkYU54EU8ypIIrCw3H3MAoOPwsvkdk+xJscdWFHRhmI0cTQdTEjZX0/VBBnMWoO5+Fs92oFj5xCRn1CCGcik5hVTnm5kU/atqNCUE+CMjZp54XQ8RKIhSl/x1WfLPHfFFdL0oRriVsAWv2DY9yqDAWMouhdPUykPocnUbUvnmzR61T0bHDtVeQyq49GPZizd+OW2T8UcpdSiIo2uZWg6pD10edv5ec1/Nh6vG2QkzObZAaDeZXUs076nuoOdhcxQej9h2tU50iPE9WCg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nuuXAS81U7/1dx+NpVd6i7wtY6SYVksqxoeWM8yKBWkyPKHrknqQAlEBgTcFTFX38UpNJfXHEST4zOE8XPx0gcPp3mNx611Vk5IhyNE6nVPq6SeVxCjjqSjIvjKVrDVBOi25rSx2LFkBCQ1Z5qwgXCZiztsgpstu1AWe7fIVX2XI2h+MYhWRP1Dq1+PQoCX/N20xq5KQWSe4HiOLh3WOgWlIuZ0oBE9Oz+bggfLWr8/kSPK4lGPw/A5WTSYYoV41YpiufTghwqqt7obK5o9VqrJpJ2iFeH8juGWJog2iMYGFb+ZMOyBOy3kEtgiq3fzT5s3jub3rjMO4jVOmMx9LyA==
  • 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: AQHYygOhe5PApRl0gUybVfXJ+E9Vsq3ifG+AgADClTU=
  • Thread-topic: [cu-dev] Please confirm: no Incompatibilities for Concurrency 3.0?
+1 I'm not aware of anything either.

Steve

From: cu-dev <cu-dev-bounces@xxxxxxxxxxx> on behalf of Nathan Rauh <nathan.rauh@xxxxxxxxxx>
Sent: Friday, September 16, 2022 9:09:31 PM
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Subject: Re: [cu-dev] Please confirm: no Incompatibilities for Concurrency 3.0?
 

Ed,

 

To my knowledge no removals, incompatibilities, or deprecations were introduced.

 

Your draft document looks good, with one minor comment being that we should use the same case for completion stages and completable futures, either both with a capital first letter or neither, in:

“Context-aware completion stages and Completable Futures”

 

 

From: cu-dev <cu-dev-bounces@xxxxxxxxxxx> on behalf of Ed Bratt <ed.bratt@xxxxxxxxxx>
Date: Friday, September 16, 2022 at 2:36 PM
To: cu developer discussions <cu-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] [cu-dev] Please confirm: no Incompatibilities for Concurrency 3.0?

Please confirm: no Incompatibilities for Concurrency 3. 0? Hi there, I'm in the process of updating the Concurrency 3. 0 Spec. page to conform with a new template we've developed in the specification committee. A new heading that we want all

ZjQcmQRYFpfptBannerStart

This Message Is From an External Sender

This message came from outside your organization.

ZjQcmQRYFpfptBannerEnd

Hi there,

I'm in the process of updating the Concurrency 3.0 Spec. page to conform with a new template we've developed in the specification committee. A new heading that we want all specifications to include is 'Removals, deprecations or backwards incompatible changes.' I believe the original Plan for, 3.0 was rather broad and we could have introduced incompatibilities. I don't see anything in either the 3.0 Release tag, nor is there anything that jumps out from the written 3.0 Specification. My recollection of this discussion when we held the Plan ballot was: the project wasn't planning any incompatible changes, but we also wanted to use the major release bump based on the scope of the proposed work.

Now that it is done, I just feel compelled to confirm this (new) section should remain blank. Can I get a nod or +1 just to put my mind at ease on this?

You can view my work in progress with the new template, in my personal fork, here. I plan to submit a PR to update the Specifications repository, once this has mellowed a couple of days, or if I can get a confirmation reply to this note. The team may, of course, add any text if there is anything it thinks the users might need to know, to use v3.

Thanks,

-- Ed

Back to the top