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

update install instructions to reflect the further documentation link #992

Closed
wants to merge 1 commit into from

Conversation

fitzjohnit
Copy link
Contributor

the current composer install instruction below doesn't work:

"openmage/magento-lts": "1.9.4.x"

so have updated to reflect the instructions in http://www.openmage.org/magento-lts/install.html that do

@Flyingmana
Copy link
Contributor

There is a bit of confusion.
The part for the Magento Releases regarding branches is still correct.

the branches for them are still 1.<minor>.<revision>.x

We do have additionally our own Major Versions with own branches http://www.openmage.org/supported-versions.html

@colinmollenhour
Copy link
Member

Maybe we should add a branch alias so people can install using dev-master?

{
   ...
    "extra": {
        "branch-alias": {
            "dev-master": "1.9.4.x"
        }
    }
}

@@ -7,18 +7,18 @@ level of backwards compatibility to the official releases.
**Pull requests with unofficial bug fixes and security patches from the community are encouraged and welcome!**

Though Magento does not follow [Semantic Versioning](http://semver.org/) we aim to provide a workable system for
dependency definition. Each Magento `1.<minor>.<revision>` release will get its own branch (named `1.<minor>.<revision>.x`)
dependency definition. Each Magento `1.<minor>.<revision>` release will get its own branch (named `1<minor>.<revision>.x`)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This line needs to be changed to ..x

that will be independently maintained with upstream patches and community bug fixes for as long as it makes sense
to do so (based on available resources). For example, Magento version `1.9.3.4` was merged into the `1.9.3.x` branch.
to do so (based on available resources). For example, Magento version `1.9.3.4` was merged into the `19.3.x` branch.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No. There was no 19.3.x branch ... it was 1.9.3.x.


## Installation

Download the latest archive and extract it, clone the repo, or add a composer dependency to your existing project like so:

```json
"openmage/magento-lts": "1.9.4.x"
"openmage/magento-lts": "19.4.x"
Copy link
Contributor

@sreichel sreichel Aug 22, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be a release number or branch ... it's neither nor (also before)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants