[SYCL] Bump the version 6.2.0->7.0.0 and update the versioning section in docs #6856
Conversation
sycl/doc/developer/ABIPolicyGuide.md
Outdated
There was a problem hiding this comment.
When would "unless it had been bumped before in this development cycle" ever apply?
Unlike previous releases we change the policy of bumping the version to be done at the beginning of the development cycle instead of its end. That allows customers who are using development snapshots to guard their code in a way that would keep working after the actual release is done. The documentation for this is being done as #6856 We have consensus on how/when MAJOR/MINOR have to be bumped, so do it now. There are some debates regarding PATCH/DEV versions updates so the documentation would be updated later.
|
@aelovikov-intel should we un-draft and finalize this? |
|
We need to discuss (probably offline via a call) on how to deal with PATCH/DEV increments, i.e. if we want them or not. |
|
This pull request is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be automatically closed in 30 days. |
aelovikov-intel
force-pushed
the
versioning-change
branch
from
6fd9d0b to
f129cdc
Compare
aelovikov-intel
changed the title
|
CUDA's |
|
L0 GEN9 Linux seems to be stuck due to infrastructure problems (1.5 hour on "Set up job" stage). I think we can merge this in because that task passed on a previous revision of this PR (https://github.com/intel/llvm/actions/runs/4787697483). |
5 participants
No description provided.