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

The encoding test should be reviewed #35

Open
heidivanparys opened this issue Nov 27, 2017 · 3 comments
Open

The encoding test should be reviewed #35

heidivanparys opened this issue Nov 27, 2017 · 3 comments

Comments

@heidivanparys
Copy link

There are two issues with the encoding test:

@cportele
Copy link
Collaborator

I agree. I think that resolving the two referenced issues should also resolve this issue. The 2016.3 sub-group should discuss and decide what should be done.

@heidivanparys
Copy link
Author

@michellutz I think this issue should have the "for-2017.4-discussion" label.

@michellutz
Copy link

Implementation of the agreed resolutions for the two issues is progressing. I therefore propose to remove the "for-2017.4-discussion" label.

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

3 participants