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

dev/release#17 - Synchronize version#s for core and core-extensions #20303

Merged
merged 4 commits into from
May 17, 2021

Conversation

totten
Copy link
Member

@totten totten commented May 14, 2021

Overview

This simplifies the management of version-numbers for core extensions.

See also: https://lab.civicrm.org/dev/release/-/issues/17

Before

Each core-extension has its own version-number. These are often neglected (e.g. not incremented in tandem with the main release).

After

Whenever we update the version-number for civicrm-core, it will also update the version-numbers for each core extension.

Comments

Some core extensions are in an alpha/beta stage. Currently, for a user who browses the list of available extensions, the "Version" column signals this. However, if the version-numbers are sync'd, then this will no longer provide that signal.

A parallel PR (#20302) updates the extension UI so that the <develStage> is communicated more effectively.

ping @colemanw

@civibot
Copy link

civibot bot commented May 14, 2021

(Standard links)

@civibot civibot bot added the master label May 14, 2021
@colemanw
Copy link
Member

Good change!

@colemanw colemanw merged commit 7ec6a5a into civicrm:master May 17, 2021
@totten totten deleted the master-extver-xml branch May 17, 2021 22:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants