No releases anymore?

[aterjung]

Hi community,

if im right, we don`t have a new release for more than a half year? What is the reason for this. Is it lack of time or a conscious decision?

[Flyingmana]

Hi, I can only speak for myself, but there its because of a lack of time, or rather a lack of usable time.
I had to realize last year, that my health/mental health reached a state, where I had problems to constantly concentrate on a single thing for more then an hour. Which causes issues, because the current release process when done carefully, takes several hours of concentrated work.

Therefore, a while back, I made a plan to reduce the load the release process causes, and make it a bit more flexible.
you can find it here: #2009
The biggest change is the introduction of release branches, so newly merged PRs can not conflict with the Release process, in case it takes a bit longer, or we need a bit extra time for merging security related changes.
As there were no complaints yet about the proposal, its probably safe to start the next release like described there.

Still, getting support with scripting of some of the steps would really help, as Iam not sure when I will be able to take these part on, and it would help a lot.

Also, Iam good, Iam not in a state where one needs to worry. Iam getting better. But its taking time, and the state of the world is not helping.

tl;dr: its available time. You can help here with contributing to the linked Ticket, and/or taking over some of the steps there.

[addison74]

This project is already starting to lose interest. The latest version of OpenMage was released last August. It's been 8 months since then, never before. It would be a shame to pull the shutters.

[tmotyl]

The current blocker to solve to be able to merge any PR or do a release is to fix compatibility of composer installer with newer composer version.
The fix is already merged in composer installer https://github.com/Cotya/magento-composer-installer/commits/main but is not yet released.

So if you want to help -> please test the master branch of composer-installer in your projects and check if its still working.

[tmotyl]

one more patch in this area waiting for review Cotya/magento-composer-installer#202

[fballiano]

@tmotyl how can I test it? I've never used M1 with composer

@addison74 I've been approved as a maintainer this morning (thank you @Flyingmana), I'll try to put some energy into our beloved OM

[addison74]

@fballiano - I'm glad for your new assignment in this project. You really have all the knowledge you need to help us move forward. So far I've worked very well with you. Personally, I do not plan to change the platform too soon as long as OM works very well where I installed it and manage it.

[tmotyl]

one more patch in this area waiting for review Cotya/magento-composer-installer#202

merged.

[tmotyl]

Hi
As composer installer is now green again, and there were several patches merged to 1.9.4.x, can we plan a 1.9.4. and 20. releases?
I think we should do a release before a security release, to make security release smaller, less risky.
@Flyingmana can you run the release (or maybe we can do it together during video call -> to share the knowledge)?
Is the patch #2009 a blocker for the release?

[fballiano]

I'd love to have the release process recorded in a video for future help.

Sorry I was absent this last week but I was/am dealing with flu :-\

[Flyingmana]

@fballiano I actually did record one of the Releases already :) thanks for reminding to share it https://youtu.be/TNgvvXJRiJo

@tmotyl not a blocker, just what would make it easier/less work.
a "full" process with all steps is also listed in https://github.com/OpenMage/organizational-internal/blob/main/release-process.md
If its on the weekend or evenings (german time), I can make myself available to assist

[alexh-swdev]

Wow, more than one hour per deploy? I never expected it to be such a long process.
So again: Thanks for your time (and I am sorry I simply have none to be of any assistance)!

[luigifab]

I tried to update our website to test all changes for the next release.
First I fetch and merge 1.9.4.x and 20.0 of my fork with Github:

Then I git pull my local clone, git checkout 20.0, git pull, git merge --no-ff 1.9.4.x. Some conflict to resolve.

---

Due to amount of changes, I did the following before apply the update on our website managed with composer:

• cd web/ (our magento-root-dir)
• git status: the working copy is clean

Apply #1834 and #1846:

• find app/ lib/Varien/ lib/Magento/ lib/Mage/ -name "*.xml" -print0 | xargs -0 geany
• Replace "<?xml" by "<?xml", then save all, then close all, then quit (my Geany is configured to trim tailling whitespace on save)
• find app/ lib/Varien/ lib/Magento/ lib/Mage/ -name "*.php" -print0 | xargs -0 geany
• Replace "<?php" by "<?php", then save all, then close all, then quit
• find lib/Zend/ -name "*.php" | xargs geany
• Replace "<?xml" by "<?xml", then save all, then close all, then quit
• find lib/Zend/ -name "*.xml" | xargs geany
• Replace "<?php" by "<?php", then save all, then close all, then quit
• git diff --ignore-all-space app/code/core/ lib/Varien/ lib/Magento/ lib/Mage/ lib/Zend/ app/design/adminhtml/default/default/layout/bundle.xml app/design/adminhtml/default/default/layout/catalog.xml app/design/adminhtml/default/default/layout/centinel.xml app/design/adminhtml/default/default/layout/downloadable.xml app/design/frontend/base/default/layout/cms.xml app/design/frontend/base/default/layout/weee.xml app/design/frontend/rwd/default/layout/cms.xml
• git add app/code/core/ lib/Varien/ lib/Magento/ lib/Mage/ lib/Zend/ app/design/adminhtml/default/default/layout/bundle.xml app/design/adminhtml/default/default/layout/catalog.xml app/design/adminhtml/default/default/layout/centinel.xml app/design/adminhtml/default/default/layout/downloadable.xml app/design/frontend/base/default/layout/cms.xml app/design/frontend/base/default/layout/weee.xml app/design/frontend/rwd/default/layout/cms.xml
• git checkout app/code/local/ app/code/community/
• Check if there are other changes, then git checkout to revert them
• git commit
• git status: the working copy is clean

Apply #1995:

• grep -Hrnl "Retrive " app/code/core/ | xargs geany
• Replace (case sensitive) "Retrive " by "Retrieve ", then save all, then close all, then quit
• grep -Hrnl "retrive " app/code/core/ | xargs geany
• Replace (case sensitive) "retrive " by "retrieve ", then save all, then close all, then quit
• grep -Hrnl "Retrive " lib/Zend/ | xargs geany
• Replace (case sensitive) "Retrive " by "Retrieve ", then save all, then close all, then quit
• grep -Hrnl "retrive " lib/Zend/ | xargs geany
• Replace (case sensitive) "retrive " by "retrieve ", then save all, then close all, then quit
• git diff
• git commit
• git status: the working copy is clean

---

Now I copy/paste app/ js/ lib/ shell/ skin/ from branch 20.0 of my OpenMage fork to our website.
Because I applied #1835, I run:

• find web/app/code/core/ web/shell/ web/lib/Varien/ web/lib/Magento/ web/lib/Mage/ web/lib/Zend/ web/lib/Unserialize/ -name "*.php" -exec php convert.php -w "{}" \;

Then I applied our other changes (don't do the same):

• rm web/js/lib/jquery/jquery-1.10.2.js
• rm web/js/lib/jquery/jquery-1.10.2.min.js
• rm web/js/lib/jquery/jquery-1.10.2.min.map
• rm web/js/tiny_mce/plugins/media/moxieplayer.swf
• rm web/skin/adminhtml/default/openmage/favicon.ico
• rm web/app/locale/*/template/email/admin_password_new.html
• rm web/js/index.php
• rm -r web/app/design/adminhtml/default/default/etc/
• rm -r web/app/design/adminhtml/default/default/locale/
• rm -r web/app/design/install/
• rm -r web/skin/install/
• rm -r web/skin/adminhtml/default/default/images/paypal web/app/code/core/Mage/Paypal web/app/code/core/Mage/PaypalUk
• rm -r web/app/design/adminhtml/default/default/template/paypal web/app/design/frontend/base/default/template/paypal web/app/design/frontend/rwd/default/template/paypal
• rm -r web/skin/adminhtml/default/default/images/paypal*
• rm web/app/locale/en_US/Mage_Paypal.csv web/app/locale/en_US/Mage_Paypaluk.csv
• rm web/skin/frontend/rwd/default/scss/module/_paypal.scss
• rm web/app/design/frontend/base/default/layout/paypal.xml
• rm web/app/design/frontend/base/default/layout/paypaluk.xml
• rm web/app/design/frontend/rwd/default/layout/paypal.xml

And:

• git co web/skin/adminhtml/default/default/custom.css web/js/tiny_mce/tiny_mce.js web/app/design/adminhtml/default/default/locale/*/translate.csv

And (with some conflict to resolve):

• git apply 1-custom.diff
• git apply 2-ie-no-more.diff
• git apply 3-pull.diff
• git apply 4-pull-1066.diff
• git apply 4-pull-1379.diff
• git apply 4-pull-1397.diff
• git apply 4-pull-1442.diff
• git apply 4-pull-1470.diff
• git apply 4-pull-1739.diff
• git apply 4-pull-1916.diff
• git apply 4-pull-9999.diff (remove mage_persistent)
• git apply 5-company.diff

Then, the git status is small, now I checking changes before test them.

[Flyingmana]

I think it looks fine, so yes, publishing it is ok

[fballiano]

And we have the new releases available for everyone!

Now I think only you can merge the release-20 branch into the 20.0 branch :-)

Great honor for me :-)

[addison74]

Good job folks. This one includes a long list of PR's. Let's hope we don't get more issues with this release :)

[Flyingmana]

good job.
will not come to it today, but you can also take the route over a PR to merge the releases back to the branches, then you do not depend on me having time

[fballiano]

Nice, although this way it will generate a line for the next changelog that we’ll have to remember to remove.

[Flyingmana]

is the question answered now?

I would say we now have regular releases again

[sreichel]

Questions was asked before https://github.com/OpenMage/magento-lts/releases/tag/v19.4.16.

-> solved?