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

psiphon: make sure data format matches old implementation #128

Closed
bassosimone opened this issue Nov 29, 2019 · 1 comment
Closed

psiphon: make sure data format matches old implementation #128

bassosimone opened this issue Nov 29, 2019 · 1 comment
Assignees
Labels
effort/M Medium effort priority/high High priority technical task technical tasks e.g. deployment wontfix This will not be worked on

Comments

@bassosimone
Copy link
Member

This calls for making sure the output of the new implementation of Psiphon matches exactly the output of the old implementation of Psiphon (modulo differences like JSON rather than YAML).

@bassosimone bassosimone added the technical task technical tasks e.g. deployment label Nov 29, 2019
@bassosimone bassosimone self-assigned this Nov 29, 2019
@bassosimone bassosimone added effort/M Medium effort priority/high High priority labels Nov 29, 2019
@bassosimone bassosimone added the wontfix This will not be worked on label Dec 3, 2019
@bassosimone
Copy link
Member Author

I have explained in #144 why a 100% matching with the old data format is neither possible nor desirable, so I am going to close this issue as wontfix. I will do my best to clarify in the spec what is the expected data format for the previous version of psiphon.

@hellais hellais added this to Backlog in DRL Anticensorship via automation Dec 16, 2019
@hellais hellais moved this from Backlog to Done in DRL Anticensorship Dec 16, 2019
@hellais hellais added this to the Sprint 1 - Parrotfish milestone Dec 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/M Medium effort priority/high High priority technical task technical tasks e.g. deployment wontfix This will not be worked on
Projects
Development

No branches or pull requests

2 participants