-
Nemanja Glumac authored
We have to sets of functions that deal with the information about Metabase version. 1. During build process we create `version.properties` file 2. During release we create new `version-info.json` or `version-info-ee.json` files that we store in AWS The first contains the information about the current Metabase version. It's used to generate info in "About Metabase" window, among others. Calling both namespaces `version-info` leads to unnecessary confusion. This commit should make the disctinction between the two more obvious and clear.
Nemanja Glumac authoredWe have to sets of functions that deal with the information about Metabase version. 1. During build process we create `version.properties` file 2. During release we create new `version-info.json` or `version-info-ee.json` files that we store in AWS The first contains the information about the current Metabase version. It's used to generate info in "About Metabase" window, among others. Calling both namespaces `version-info` leads to unnecessary confusion. This commit should make the disctinction between the two more obvious and clear.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.