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.

Sign up for GitHub

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

Jump to bottom

Create v2 development branch #63

Closed
amercader opened this issue Jul 28, 2022 · 1 comment · Fixed by #66
Closed

Create v2 development branch #63

amercader opened this issue Jul 28, 2022 · 1 comment · Fixed by #66
Assignees
@aivuk
Labels
v2
Milestone
v2

Comments

@amercader
Copy link
Member

All the new work we have planned for v2 (see #61) should be done in a new branch which will we Python 3 only. Let's branch a dev-v2 branch from current master and do a bit of cleanup to remove old CKAN versions, py2/py3 hacks etc:

  • Test on 2.9 only
  • Remove six
  • Remove fanstatic/assets support (eg stuff like this
  • Remove compatibility hacks in tests like this one
  • etc

Once that branch is ready, we'll create features branches for v2 from that one
@amercader amercader added the v2 label Jul 28, 2022
@amercader amercader mentioned this issue Jul 28, 2022
Closed
@amercader amercader added this to the v2 milestone Jul 28, 2022
@aivuk aivuk mentioned this issue Jul 28, 2022
Merged
@amercader
Copy link
Member Author

Done, development following in the dev-v2 branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aivuk aivuk

Labels
v2
Projects
None yet
Milestone
v2
Development

Successfully merging a pull request may close this issue.

Create v2 branch with support to Py3 and CKAN >= 2.9 only ckan/ckanext-validation
2 participants
@amercader @aivuk