Version bump

[fballiano]

Since we just merged pretty important stuff, but at the same time we need more testing-time, what about a next version like 20.1.0-rc1 and 19.5.0-rc1?

Related PRs

• Moved phpseclib, mcrypt_compat, Cm_RedisSession, Cm_Cache_Backend_Redis and Pelago_Emogrifier to composer #2411
• Replace lib/Zend with shardj/zf1-future 🚀  #2827

[sreichel]

Does upper/lower-case matter?

[sreichel]

... but ... we have an error that sould be fixed. If its okay i'd remove latest release from packagist.org.

[fballiano]

Does upper/lower-case matter?

I don't think so, I used lowercase since it was already in the sample (comment next to the "alpha/beta/rc" like)

[fballiano]

... but ... we have an error that sould be fixed. If its okay i'd remove latest release from packagist.org.

but how can we fix that anyway now?
they only way would be to create a branch from the currently released tag, fix the typo manually and release that, without PRs etc..

[sreichel]

You are doing the releases. Is it much work to make that hotfix release?

We could fix this bug w/o enforce to update to Zend-changes.

[fballiano]

@sreichel in this case it's pretty easy, I've already created branch https://github.com/OpenMage/magento-lts/tree/19.4.21 with just 2 commits. they're pretty basic so everything should be ok. can you check it out a second and then I'll release?

also, it's a v19 hotfix only because v20 doesn't have the bug with #2793

[sreichel]

Perfect.

[Flyingmana]

... but ... we have an error that sould be fixed. If its okay i'd remove latest release from packagist.org.

be very very very careful with removing releases, this is going to break anyone who uses this in their composer.json or composer.lock.
Replacing it does not work anyway, as it would have a different checksum and cause fails.

[fballiano]

We’ll not remove anything don’t worry

[sreichel]

... but ... we have an error that sould be fixed. If its okay i'd remove latest release from packagist.org.

be very very very careful with removing releases, this is going to break anyone who uses this in their composer.json or composer.lock. Replacing it does not work anyway, as it would have a different checksum and cause fails.

Thanks. This is why i asked for.

Is there another propper way to avoid installing "bugged" releases?

Something like a required extension that cant we installed with certain releases?

Replacing it does not work anyway, as it would have a different checksum and cause fails.

I'd not re-add it. If its bugged it should be not available to install. However ... not going to touch this.

[fballiano]

Tomorrow morning I’ll release the new v19 and there will be no problem anymore 😉

[fballiano]

19.4.21 is released, I was afraid of the process but at the end of the day it was pretty easy and I should have done it ealier.. it's done anyway now.

[Flyingmana]

Since we just merged pretty important stuff, but at the same time we need more testing-time, what about a next version like 20.1.0-rc1 and 19.5.0-rc1?

regarding the original question, can you link this very important stuff?
Generally I would say, releasing alpha,beta,rc releases is always okay.

But I wonder what it is, that requires the minor version bump, especially for the 19. release

[fballiano]

it's the drop of CM modules and ZF1 moving them to composer

[fballiano]

linkedin the PRs in the description. I think the bump should be minor, not your patch version

[Flyingmana]

it's the drop of CM modules and ZF1 moving them to composer

I see, that surely is a good reason for a minor version bump. And also a good reason for RC Tagging.