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

V1.0 breaking changes #261

Closed
wants to merge 13 commits into from
Closed

V1.0 breaking changes #261

wants to merge 13 commits into from

Conversation

tmadlener
Copy link
Contributor

@tmadlener tmadlener commented Feb 1, 2024

This is a PR that is not intended to be merged! It collects all the upcoming breaking changes in one place for easier testing of the final result after all of them have been merged. It currently contains the changes from:

More changes are still to come and will show up here as soon as they are ready. Please use the dedicated PRs for mentioning specific issues that are caused / raised by them.

@wdconinc this is a sort of WIP of the branch we discussed at the last Key4hep meeting.

Also tagging @BrieucF @kjvbrt and @mirguest as these will almost certainly also affect you.

@tmadlener tmadlener marked this pull request as draft February 1, 2024 15:18
@tmadlener tmadlener force-pushed the v1.0-breaking-changes branch 2 times, most recently from 185bd20 to 8a534b8 Compare February 8, 2024 10:21
edm4hep.yaml Outdated Show resolved Hide resolved
@jmcarcell
Copy link
Contributor

Should we have a branch like this one in every affected repo? Otherwise it's impossible to test it, and should have the same name obviously

@jmcarcell
Copy link
Contributor

At this point this PR is not useful since all but one of the PRs have been merged and this one isn't up to date

@jmcarcell jmcarcell closed this Feb 23, 2024
@jmcarcell jmcarcell deleted the v1.0-breaking-changes branch October 29, 2024 10:10
@wdconinc
Copy link
Contributor

wdconinc commented Nov 21, 2024

This was not quite the descriptive PR title that I thought it was, and it is turning out to be quite annoying to deal with for us due to the removal of the vector member of raw hits in TrackerHit. Same for ACTS, which is relying on the raw hits. Edit: ACTS abuses this somewhat, but we are using this in the intended way: to refer to raw hits.

@wdconinc
Copy link
Contributor

This is what causes us to move more datatypes into EDM4eic instead of using EDM4hep 🤷

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.

3 participants