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

CKAN Roadmap and v3 in particular #248

Open
rufuspollock opened this issue May 14, 2020 · 3 comments
Open

CKAN Roadmap and v3 in particular #248

rufuspollock opened this issue May 14, 2020 · 3 comments
Assignees

Comments

@rufuspollock
Copy link
Member

Current page is out of date https://ckan.org/developers/roadmap/ and could do with anb upda

There's also a discussion to be had about what we want to see in CKAN v3

Initial Thoughts (presented on tech team call 14 May 2020 by @rufuspollock)

Comments welcome

https://docs.google.com/document/d/1Bv-01m6_jKExs78foS9kbeyymhUom-idZJ8D4wQ_erE/edit#

Previous discussion (Aug-Sep 2018)

See https://lists-archive.okfn.org/pipermail/ckan-dev/2018-August/022860.html

https://docs.google.com/document/d/1qxU-wkUBf7BgMsBzOvMUKNcyYCyzBsbNQoKtdioRReg/edit#heading=h.ka47zlvu99u

@rufuspollock rufuspollock self-assigned this May 14, 2020
@wardi
Copy link
Contributor

wardi commented Jun 30, 2020

I created a milestone for some important features it would be nice to have merged for 3.0 https://github.com/ckan/ckan/milestone/14

@jasonlally
Copy link

Hello, just wondering which is the official record for roadmap plans for CKAN 2 and 3? Where should I be looking for the source of truth so to speak :-) @rufuspollock

@wardi
Copy link
Contributor

wardi commented Jun 9, 2021

The only truth is code that's working, reviewed, and merged 😎

This repo is no longer updated but some of the current important feature work has been collected under https://github.com/ckan/ckan/projects/4 which we're trying to keep up to date.

The next release is slated to be called "2.10" for now; we've been saving "3.0" for a release with big incompatible changes. I think our next release is a good candidate for a "3.0" because it's python3-only but there's no consensus in the core team yet.

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