Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SYCL][Doc] Add release notes for September release #4852

Merged

Conversation

romanovvlad
Copy link
Contributor

No description provided.

@romanovvlad
Copy link
Contributor Author

A little bit late...
Thanks @s-kanaev and @vladimirlaz for help.

sycl/ReleaseNotes.md Outdated Show resolved Hide resolved
- Fixed imbalance in events release and retain in Level Zero plugin [6117a1b]

## API/ABI breakages

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
None

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

None?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Funny enough, but massive API "removals" didn't get into the commits range for the release. So, it seems we have only one API breakage here.

Comment on lines 207 to 208
- [new] Filenames are removed from diagnostic to avoid leaks of full paths
from build environment [6bbfe42b3]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it's an issue. It's a change and it's a fix.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Moved to bug fixes section.

@pvchupin pvchupin requested a review from AaronBallman October 29, 2021 18:03
@AaronBallman
Copy link
Contributor

Should our release notes attempt to convey which Clang revision we are most closely a downstream of? e.g., so users know this is more closely related to future-Clang 14 vs current-Clang 13. (Giving users this information helps them to better understand how much of Clang's features they can expect to work here.)

@romanovvlad
Copy link
Contributor Author

Should our release notes attempt to convey which Clang revision we are most closely a downstream of? e.g., so users know this is more closely related to future-Clang 14 vs current-Clang 13. (Giving users this information helps them to better understand how much of Clang's features they can expect to work here.)

Suggestion is to include the hash of the latest llvm.org commit that was in intel/llvm , right?
For example, for this release we would have 83ddfa0.

@romanovvlad romanovvlad requested a review from pvchupin November 1, 2021 10:24
pvchupin
pvchupin previously approved these changes Nov 1, 2021
sycl/ReleaseNotes.md Outdated Show resolved Hide resolved
sycl/ReleaseNotes.md Outdated Show resolved Hide resolved
sycl/ReleaseNotes.md Outdated Show resolved Hide resolved
sycl/ReleaseNotes.md Outdated Show resolved Hide resolved
@romanovvlad romanovvlad merged commit d40e028 into intel:sycl Nov 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants