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

Define serialization transition period length and prepare removing old routines #274

Open
lumip opened this issue Jun 16, 2018 · 3 comments
Assignees

Comments

@lumip
Copy link
Contributor

lumip commented Jun 16, 2018

We must define a transition period during which the old routines are deprecated but still available and, preferably, already prepare a branch where they are removed which is to be merged after the transition period expires.

@lumip lumip added this to the New Serialization Routines milestone Jun 16, 2018
@lumip lumip changed the title Define transition period length and prepare removing old routines Define serialization transition period length and prepare removing old routines Jun 17, 2018
@terrorfisch
Copy link
Member

terrorfisch commented Jul 6, 2018

We should be able to load all old pulses anytime.

We should however remove the old writing routines. Maybe by the end of the year?

@terrorfisch
Copy link
Member

The old writing routines will be dropped on the 1.0 release. They will be deprecated in the next release.

@terrorfisch
Copy link
Member

They are already deprecated.

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