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

Plone 5 #184

Closed
76 of 90 tasks
davisagli opened this issue Feb 25, 2014 · 11 comments
Closed
76 of 90 tasks

Plone 5 #184

davisagli opened this issue Feb 25, 2014 · 11 comments

Comments

@davisagli
Copy link
Sponsor Member

This is a summary of tasks that need to be done to complete Plone 5.

It is a work in progress. In particular we need to fill in issues related to theming, mockup, plone.app.contenttypes, and new issues found via manual testing.

It is a place to reference other tickets which provide detail about particular tasks. Ideally, each task should be something that could be completed by a motivated person in a day or two. Larger efforts should be broken into smaller pieces.

Ready for review

To do

Theming

Javascript (Mockup)

Migration

Member-related (will be focus of Emerald Sprint)

Cleanup

Misc

Bugs

Note: tasks considered blockers for a Plone 5 beta release are marked as BLOCKER

@davisagli davisagli added this to the Plone 5 milestone Feb 25, 2014
@acsr
Copy link

acsr commented Jun 13, 2014

I miss here any i18n l10n related topic either checked or unchecked. I stumbled over the missing i18n support in the new foldercontents implementation some days ago and investigating a solution to fix this for wildcard.foldercontents in Plone 4 as well.

Can someone with the necessary overview please add this here as well?

I can add my research results elsewhere once I found the right place. So having this here would be a good starting point. Thanks for this overview!

@gforcada
Copy link
Sponsor Contributor

gforcada commented Nov 5, 2014

@gforcada
Copy link
Sponsor Contributor

gforcada commented Nov 5, 2014

@tisto @bloodbare most probably we need to create tickets and some explanation for them, no pressure, but as the authors of the documents maybe your insight is helpful to drive that document to tickets :)

@vincentfretin
Copy link
Member

We need some love on i18n, I created a separate issue with all the i18n issues I found in november:
#379

@vangheem
Copy link
Member

Definitely. It'd be good if someone went through all the javascript and made sure i18n wrappers were used everywhere there is text also.

@jensens
Copy link
Sponsor Member

jensens commented Nov 4, 2015

Plone 5 is released. I close this one.

@jensens jensens closed this as completed Nov 4, 2015
@gforcada
Copy link
Sponsor Contributor

gforcada commented Nov 4, 2015

🎉

@hvelarde
Copy link
Member

hvelarde commented Nov 4, 2015

yes, Plone 5 is relased but there are some important issues that MUST be fixed and we need to keep an eye on them.

one item needs special attention:

  • BLOCKER Registry migration (from Resource Registry) (no issue)

also note that these ones need huge deprecation warnings on Plone 4 and Plone 5:

@gforcada
Copy link
Sponsor Contributor

gforcada commented Nov 4, 2015

@hvelarde create issues for all of them and add milestone 5.0.x on them, this one was a tracker for 5.0 which is out.

@gforcada gforcada modified the milestones: Plone 5.0, Plone 5.1 Nov 4, 2015
@hvelarde
Copy link
Member

hvelarde commented Nov 4, 2015

done!

@jensens
Copy link
Sponsor Member

jensens commented Nov 4, 2015

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants