Skip to content
This repository has been archived by the owner on Jan 17, 2025. It is now read-only.

Verify for WordPress 6 #158

Closed
TimidRobot opened this issue Apr 29, 2021 · 3 comments · Fixed by #198
Closed

Verify for WordPress 6 #158

TimidRobot opened this issue Apr 29, 2021 · 3 comments · Fixed by #198
Assignees
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟧 priority: high Stalls work on the project or its dependents
Milestone

Comments

@TimidRobot
Copy link
Contributor

TimidRobot commented Apr 29, 2021

Problem

Need to verify plugin works on the current version of WordPress and update readme.txt.

Description

Released versions since last tested

WordPress 6.0 is imminent! Are your plugins ready?

WordPress 6.0 is scheduled to be released on May 24th. Are your plugins ready?

After testing your plugins and ensuring compatibility, it only takes a few moments to change the readme "Tested up to" value to 6.0. This information provides peace of mind to users and helps encourage them to update to the latest version of WordPress. You can find more information about plugin readmes here: https://developer.wordpress.org/plugins/wordpress-org/how-your-readme-txt-works/.

Here are the current "Tested up to:" values for each of your plugins:

For each compatible plugin, you do not need to release a new version — simply update the stable version's "Tested up to" value to 6.0 in your readme file. Plugins that are not updated as tested with the latest 3 major releases of WordPress have a notice displayed on their WordPress.org plugin page noting that the plugin may no longer be maintained or supported. It's in everyone's best interest to continue testing plugins against WordPress versions and updating that value.

Looking to get more familiar with 6.0? Read this roundup post on the core development blog to learn more about the various changes coming to core with this major release:
https://make.wordpress.org/core/2022/05/03/wordpress-6-0-field-guide/

There are a few areas that need specific focus as plugin-related changes are coming in 6.0:

To ensure compatibility, here is how to download the latest release candidate for testing with your plugin: https://make.wordpress.org/core/handbook/testing/beta-testing/.

Thank you for all you do for the WordPress community, and we hope you will enjoy 6.0 as much as we do.

@TimidRobot TimidRobot added 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository labels Apr 29, 2021
@TimidRobot TimidRobot added this to the v2021.05.1 milestone Apr 29, 2021
@NicoHood
Copy link

Will this addon be updated to 5.8.x?

@Enkerli
Copy link

Enkerli commented Oct 5, 2021

Like @NicoHood, also very curious about a 5.8.x update.

Just mentioned this plugin during a Sprint report for our new site, as it'd be a neat solution for us. The site is a merge of two separate sites which have been publishing content with distinct licenses (CC-BY-NC-SA vs. CC-BY-NC-ND). We also want to make it really seamless what licenses people can choose for future items. So, I had high hopes for the plugin.

Given the fact that the plugin was flagged as untested through the last 3 major versions and that the last changes occurred 5 months ago, the webdev was reluctant to consider the plugin and might elect to do things manually.

Any insight as to the roadmap would be useful.

@brylie brylie changed the title Verify for WordPress 5.7.x Verify for WordPress 5.8.x Oct 6, 2021
@brylie brylie self-assigned this Oct 6, 2021
@brylie brylie added Hacktoberfest help wanted Open to participation from the community 🟧 priority: high Stalls work on the project or its dependents and removed 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work labels Oct 11, 2021
@brylie
Copy link
Contributor

brylie commented Oct 11, 2021

We are prioritizing this task for the current development milestone.

@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Dec 7, 2021
@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Dec 14, 2021
@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Jul 1, 2022
@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Jul 8, 2022
@possumbilities possumbilities self-assigned this Jul 15, 2022
@cc-open-source-bot cc-open-source-bot added 🏷 status: label work required Needs proper labelling before it can be worked on and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Jul 16, 2022
possumbilities added a commit that referenced this issue Jul 18, 2022
[#158] refer to gh issue, verify wp v6.0.1 tested, passes
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟧 priority: high Stalls work on the project or its dependents
Development

Successfully merging a pull request may close this issue.

6 participants