Schedule releases of CI4

Why not have the “Stable” version and a link to the GitHub “Latest/Development” version?

I definitely agree. We have lots of great additions, many bug fixes, and even a few hot new features since 4.1 - I want to get those out there! I have no problem with expectations for more frequent releases, my pushback was on expectations around a set schedule.

So what was the final decision? I think that voting for the second option is a call not to put pressure on the CI team, but it is not a decision about the release schedule of the framework.

For example, look at the list of Laravel releases https://github.com/laravel/laravel/releases and look at changelogs these are small fixes, but they are regular. I think that for the CI team to release such releases once a month will also not be very difficult.

It is also interesting to know @kilishan's personal opinion on this issue.

@John_Betong we already support development versions. You can check out the `builds` command in AppStarter - and of course for downloads one can always download the repo itself instead of the release.

@Avega I’m not sure what else you would like to know? The team has committed to more frequent releases (prior to this thread). Probably aiming for once a month would be a good target but I really really don’t want people linking this comment and being like “it’s been more than a month, where is my release??” We are poised for the next release already, just waiting on the last few Pull Requests which would constitute breaking changes were they to be considered after a release.

P.S. Regarding Lonnie, you should know that “@“ doesn’t actually mention someone on the forums. I use them informally in responses but if you want to summon Lonnie you should probably DM him or try him on Slack. He has some (good) life stuff going on right now that affects his internet and availability so he may be slow to respond.

@MGatner,
I always clone the GitHub version because I’m not a fan of using Composer plus it is far quicker.

@John_Betong we already support development versions. You can check out the `builds` command in AppStarter - and of course for downloads one can always download the repo itself instead of the release.

@Avega I’m not sure what else you would like to know? The team has committed to more frequent releases (prior to this thread). Probably aiming for once a month would be a good target but I really really don’t want people linking this comment and being like “it’s been more than a month, where is my release??” We are poised for the next release already, just waiting on the last few Pull Requests which would constitute breaking changes were they to be considered after a release.

Thanks for the reply. I really appreciate your contribution to the framework. And I completely agree with you that there are some people who will always be dissatisfied with something.

The essence of my proposal was to release releases more often than now, especially when there is already an approved set of fixes or features. And as I understand it, you agreed to this proposal.