-
Notifications
You must be signed in to change notification settings - Fork 20
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
ask: Django CMS 4.1 upgrade timeline #255
Comments
@joshyu I am not aware of a reason why djangocms-moderation would not work with djangocms-versioning 2.x (which is required, though, for django CMS 4.1). Do you have any specific issue you run into? |
@fsbraun , We haven't tested it yet. Do you think It just works ? |
It could well be. But I personally have not tested this. |
@joshyu Fabian is your man for any of the open source packages, he's done a great job of making django-cms packages community ready (django-cms 4.1+). Be sure to not add anything that is your company specific, that includes any stack traces that shouldn't be shown to the outside world. @fsbraun it might be worth showing Josh the Slack channel for the open support. |
@joshyu you should join as a member ($24 a year): https://www.django-cms.org/en/memberships/ |
Our company depends on django-cms 4.0.1.x and djangocms-moderation. Recently we are about to upgrade to django-cms 4.1.
My question is, does DC community has a timeline to upgrade djangocms-moderation to work under django-cms 4.1?
The text was updated successfully, but these errors were encountered: