[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:  has-patch         |
------------------------------+---------------------

Comment (by dufresnesteven):

 > A bit unsure what this is/how that would work? Will it be pulling
 plugin's source (assuming alpha/development version) from GitHub and
 zipping it on wp.org and letting the user download the zip? That probably
 won't work for some (many?) plugins that need to be built?

 No, it would pull in the zip file (or the source), prepare it to be
 committed to the repo as a new tag, and prompt the author for confirmation
 before doing so.

 > That probably won't work for some (many?) plugins that need to be built?

 That's the reason why the initial designs don't include GitHub
 integration. We are not sure how to handle that. Instead we could receive
 a zip artifact from a public build server and pull that in. That is
 depicted in the current designs. If that isn't deemed valuable, we can
 rethink that.

 > Also, unsure what would be the role of wp.org here? If the plugin
 authors want to make an alpha version available to users, why not
 "release" it on GitHub instead? Imho plugins that are developed on GitHub
 should always have a link to their repo there from the plugins screen on
 wp.org. Seems that would be more useful to users?

 Yep, alpha versions should not be uploaded to wp.org. Those who develop &
 release on GitHub are still able to. Those who use GitHub actions that
 push to wp.org SVN will still work the same. However, it's better UX to
 have consistency in where to locate releases on wp.org. Finding a release
 and relevant information for plugin X should be the same for plugin Y and
 I would suggest we avoid the pattern of linking users away to GitHub
 repositories or company websites to download files or understand what
 recent changes were added to the plugin that they use.

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