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

Discussion for v3.0.0 #1270

Closed
twsouthwick opened this issue Dec 19, 2022 · 2 comments
Closed

Discussion for v3.0.0 #1270

twsouthwick opened this issue Dec 19, 2022 · 2 comments
Milestone

Comments

@twsouthwick
Copy link
Member

twsouthwick commented Dec 19, 2022

We are going to address a number of technical issues that will require a major change. This version will not be binary compatible with the previous 2.x versions, but should be source compatible to a degree. We will strive to maintain a migration guide and be aware of what effects changes will have.

This issue is to raise concerns about changes that may be made for discussion. Issues and PRs for this will be flagged using the Milestone

CI builds for this will be pushed to a feed at: https://openxmlsdk.blob.core.windows.net/feed/index.json

@twsouthwick twsouthwick added this to the v3.0 milestone Dec 19, 2022
@twsouthwick twsouthwick pinned this issue Dec 19, 2022
@Asbjoedt
Copy link
Contributor

So hi there!
Thx for this issue.

I have this #1142, which is high on the agenda in my workplace, and I expect it to be similarly high on the agenda for other heritage institutions.

By the end of this year, we will conclude our project on spreadsheets preservation, and this one issue in particular, is important for us to get resolved.

@twsouthwick
Copy link
Member Author

@Asbjoedt One of the things I'm doing is cleaning up the initialization logic so the package is more customizable. I'm hoping to finish that up by the end of February. Once that's done, this kind of thing may be more possible. I'm breaking things up into replaceable parts called features.

To be honest, I'm not seeing anything in the issue that would need to be in v3.0, but the changes I'm doing for v3.0 should enable building it. Sounds like the validator system would need to be customizeable - that's something I was going to investigate after the packages and parts get cleaned up. Let's continue the conversation in #1142

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

No branches or pull requests

2 participants