Please review 1.9.3.1 import via merge about magento-lts HOT 12 CLOSED

I cannot pull that branch with composer. Any hint?

"openmage/magento-lts": "1.9.3.1-dev"

from magento-lts.

"openmage/magento-lts": "dev-1.9.3.1"?

from magento-lts.

Nope

  Problem 1
    - The requested package openmage/magento-lts dev-1.9.3.1 exists as openmage/magento-lts[1.8.0.x-dev, 1.8.1.x-dev, 1.9.0.x-dev, 1.9.1.1, 1.9.1.x-dev, 1.9.2.0-dev, 1.9.2.1-dev, 1.9.2.2-dev, 1.9.2.3-dev, 1.9.2.4-dev, 1.9.2.x-dev, 1.9.3.0-dev, dev-Flyingmana-patch-1] but these are rejected by your constraint.

from magento-lts.

OK, looks like packagist hasn't updates yet. https://packagist.org/packages/openmage/magento-lts

from magento-lts.

Richtig, danke. Lösung ist auch das Repo anzugeben:

"openmage/magento-lts": "1.9.3.1-dev“
….
{
  "type": "vcs",
  "url": "https://github.com/OpenMage/magento-lts.git"
}

from magento-lts.

thx for the hint with packagist, @drobinson can maybe speed this up a bit.
As people are already using it now, I changed the default branch so we dont get extra work with PRs.

But still, we need a review of the merge :)

from magento-lts.

We checked it and it looks pretty good. I hope to get it down a deployment pipeline later this day to test it on live conditions.

from magento-lts.

not very detailed, but highover method. installed and upgraded fom 1.9.2.4
site and works fine. Had some problem with Redis but could also be server
side.

On Wed, Nov 23, 2016 at 12:40 PM, Daniel Fahlke [email protected]
wrote:

thx for the hint with packagist, @drobinson https://github.com/drobinson
can maybe speed this up a bit.
As people are already using it now, I changed the default branch so we
dont get extra work with PRs.

But still, we need a review of the merge :)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#136 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAn0a8ATXHbZpv5LbzRdpjXkJ5gSdCtpks5rBCZAgaJpZM4K4q0d
.

from magento-lts.

@Flyingmana Did you have to manually resolve any merge conflicts? Is that what the two file paths in the commit message are referring to?

from magento-lts.

not only, they got automatically added to the message, but there was a bit more because of the file permission changes.

from magento-lts.

can we close this issue?

from magento-lts.

as there was enough time and nobody had complaints, yes

from magento-lts.