[wp-meta] [Making WordPress.org] #7783: Create a Releases page for every plugin.

[Making WordPress.org]

#7783: Create a Releases page for every plugin.
------------------------------+---------------------
 Reporter:  dufresnesteven    |       Owner:  (none)
     Type:  defect (bug)      |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------
Description changed by dufresnesteven:

Old description:

> **Proposal**
>
> Add a 'Releases' tab to each plugin to centralize release features and
> information, and promote best practices.
>

> **Context**
> Release related functionality and information appear in different places
> within the plugin directory. Some examples include:
>
> - [https://wordpress.org/plugins/developers/releases/ Release
> confirmations] have their own page.
> - Readme.txt importing issues are displayed as banners on the plugin
> homepage to authors.
> - Releases are downloadable in a plugin's Advanced View (Provided tags
> are used).
> - Changelog is displayed in the "Development" tab. (Varies from plugin to
> plugin)
>
> There are also some forward-leaning features for plugins that will also
> need a home that **may** be relevant:
> - [ticket:6087 Provide a GitHub Integration for Plugins]
> - [ticket:3845 Linting for Plugin Submissions + Filters for Plugin
> Directory Searching]
> - [ticket:5484 Add a "Tag and release" button]
> - [ticket:6939 Reporting Security vulnerabilities in plugins]
>
> **What should/could the page include?**
> - Should include release confirmations.
> - Should display import issues with specific releases.
> - Should allow users to download older versions (although not promote
> it).
> - Should strongly encourage the use of `/tags` for releases.
> - Could allow users to manually create releases using a zip/GitHub
> integration (bypassing SVN which is a barrier for some users).
> - Could display plugin check results.
> - Could display known Common Vulnerability and Exposure information to
> plugin authors.
> - Could provide release and/or performance related stats.
> - Could provide changelogs for respective release.
> - Could link to changesets to help user track changes between releases.
> - Could make it easy to test previous versions in playground.
> - ... I'm sure there's more things we can add to make it more valuable.
>
> I'm curious what ya'll think. I'm not a designer but I've attached is an
> early, lo-fi version of what's in my head.

New description:

 **Proposal**

 Add a 'Releases' tab to each plugin to centralize release features and
 information, and promote best practices.


 **Context**
 Release related functionality and information appear in different places
 within the plugin directory. Some examples include:

 - [https://wordpress.org/plugins/developers/releases/ Release
 confirmations] have their own page.
 - Readme.txt importing issues are displayed as banners on the plugin
 homepage to authors.
 - Releases are downloadable in a plugin's Advanced View (Provided tags are
 used).
 - Changelog is displayed in the "Development" tab. (Varies from plugin to
 plugin)

 There are also some forward-leaning features for plugins that will also
 need a home that **may** be relevant:
 - [ticket:6087 Provide a GitHub Integration for Plugins]
 - [ticket:3845 Linting for Plugin Submissions + Filters for Plugin
 Directory Searching]
 - [ticket:5484 Add a "Tag and release" button]
 - [ticket:6939 Reporting Security vulnerabilities in plugins]

 **What should/could the page include?**
 - Should include release confirmations.
 - Should display import issues with specific releases.
 - Should allow users to download older versions (although not promote it).
 - Should strongly encourage the use of `/tags` for releases.
 - Could allow users to manually create releases using a zip/GitHub
 integration (bypassing SVN which is a barrier for some users). Edit: No
 changes to how code is stored or deployed. SVN will still be the
 underlying version control system :).
 - Could display plugin check results.
 - Could display known Common Vulnerability and Exposure information to
 plugin authors.
 - Could provide release and/or performance related stats.
 - Could provide changelogs for respective release.
 - Could link to changesets to help user track changes between releases.
 - Could make it easy to test previous versions in playground.
 - ... I'm sure there's more things we can add to make it more valuable.

 I'm curious what ya'll think. I'm not a designer but I've attached is an
 early, lo-fi version of what's in my head.

--

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/7783#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org