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

Add to WordPress Plugins #1441

Open
candrews opened this issue May 9, 2019 · 3 comments
Open

Add to WordPress Plugins #1441

candrews opened this issue May 9, 2019 · 3 comments
Labels
discussion Needs discussion or is being discussed.

Comments

@candrews
Copy link
Contributor

candrews commented May 9, 2019

Can VersionPress be added as an official Wordpress plugin?

https://wordpress.org/plugins/developers/add/

Doing so would make it much easier for users to discover, install, and update VersionPress.

@pavelevap
Copy link
Collaborator

Previously: #1291

I do not think that adding Versionpress into official WP repository is possible until at least latest WordPress version is fully supported (Gutenberg).

@pavelevap pavelevap added the discussion Needs discussion or is being discussed. label May 9, 2019
@borekb borekb changed the title Add to Wordpress Plugins Add to WordPress Plugins May 10, 2019
@borekb
Copy link
Member

borekb commented May 10, 2019

Thanks for creating this issue. It crossed my mind several times recently as well, here are my current thoughts:

  • I'm much more open to publishing to the WordPress plugin repository than I was before, for example, I no longer think that we need to wait post the Developer Preview phase.
  • I agree with @pavelevap that Gutenberg should / must be supported first.
  • I'm quite curious how the review would go. For example, VersionPress has several system requirements that might not be available in the environment where plugin reviewers test. I guess we'll find out 😄.

Also, quite importantly, there have been discussions recently about our release process – how often to tag new releases, how to ship bug fixes, etc., see e.g. #1433. I personally think that this is a bigger question than whether we're in the plugin repository or not, and there are some complexities around it, for example, our currently documented update process makes the old commits unactionable (they can no longer be undone or rolled back to, which is a major caveat).

So before we publish, we should know answers to these questions:

  • How often do we publish?
  • If not after every merge to master, do we have another way to provide bugfix builds for those who need them?
  • What's our update process? How do we know which versions can keep the Git history and which should make it unactionable? (Migrations are a hard problem, see Migration system for vpdb / INI files #275.)

@pavelevap
Copy link
Collaborator

Related issue about updating VersionPress: #384

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Needs discussion or is being discussed.
Projects
None yet
Development

No branches or pull requests

3 participants