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

Preparation for TD Next Work #1997

Merged
merged 15 commits into from
Apr 16, 2024
Merged

Preparation for TD Next Work #1997

merged 15 commits into from
Apr 16, 2024

Conversation

egekorkan
Copy link
Contributor

@egekorkan egekorkan commented Apr 3, 2024

Given that we are not working on the TD 1.1 anymore, we can change the title, respec config, abstract and intro to match the scope of the work.

Points of discussion:

  • Should we already name it 2.0? @lu-zero 2.0 , @relu91 next is more flexible but we are already committed to 2.0. We should be all ok with 2.0 but we can do this in a follow-up
  • Temporary context URL: When doing actual changes to the information model
  • Which Editors to be used: When moving binding templates, the editors there should be moved here as well

Preview | Diff

@egekorkan egekorkan changed the title Using new respec config fields and title for TD next Preparation for TD Next Work Apr 3, 2024
README.md Outdated Show resolved Hide resolved
Co-authored-by: Jan Romann <jan.romann@hs-emden-leer.de>
@egekorkan egekorkan changed the base branch from main to wot-td-1.0 April 11, 2024 13:11
@egekorkan egekorkan changed the base branch from wot-td-1.0 to main April 11, 2024 13:11
@egekorkan
Copy link
Contributor Author

Call of 11.04: We will merge this after removing those unwanted changes in the toolchain folder. The version name will be discussed in another PR.

@egekorkan egekorkan merged commit 1e16b24 into main Apr 16, 2024
1 check passed
@egekorkan egekorkan deleted the ege-respec-config-for-tdnext branch April 16, 2024 11:19
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.

None yet

2 participants