UNA 14
I suggest in future updates do small update improvements periodically instead of having them all lumped in UNA 14. Waiting for UNA 13 for almost a year is a reminder of what we don't want for UNA 14.
-
I agree :)
-
This is why cooperate and other software and website companies/Developers do increment upgrades and updates. They get the main software out there, and then make updates to what has issues... The long wait can drive people away. So they keep people intrigued by adding and adjusting as they go.
The last I thought, was this UNA 14 was supposed to hit us in mid 22? We still await.
-
Maybe it's better if releases are not rushed so that when they do roll out they are more stable? Apparently, UNA 13 still has issues so why talk about 14?
-
Regular small updates help site owners see if the updates create more bugs and if so can help solve them. If someone has dozens of different apps from different vendors then they can trace the issues faster than say an update that has over 300 changes. Before 13 UNA rolled out updates that were easier to track and quicker to fix and developers could also catch up and update their apps. Bigger longer updates break sites completely and costs more for the site owners that have to wait for mod developers to sort out and update. If you have custom work done it's even harder and more costly. There really is no such thing as "wait until all bugs are fixed" because updates always create more bugs.
-
what @Will Roberts writes was also my speech before and I can only agree with him. It is not possible that we wait here half a year or 3/4 year wis a release appears. You should not underestimate the costs if you roughly extrapolate everything in the month, (with streaming) and (without third party modules buy) then just 300 - 400 euros go here.
-
There are no such things "bug free", its just part of updating and changes, really.
-
I suggest regular updates and security fixes every 2-3 months. And do hot fixes like as soon as the bug is fixed just update it right away.
-
I completely agree that more frequent updates would be preferable. In some cases, like with v13, it is difficult to split up the updates because we have to complete a makeover of some sort that can not be delivered in parts. In this case it was priority about adopting TailwindCSS for frontend styling. Just couldn't go half-way in many aspects. And while we're working on such a makeover there's usually a bunch of new features and implements that get pushed from tailored implementation projects or are required for us to be able to deliver a client project. 4-6 months cycle would be most ideal for us - not too far apart as to make updates cumbersome, and not too frequent as to make people loathe constant need to update.
UNA 14 is meant to be a follow-up update focusing on user-experience improvements and general performance. So, instead of building new modules we plan to work through existing modules and make them better. This will also allow us to release sooner.
-
I don't care if alpha or beta versions are still buggy, that's their purpose. But I hope, that the update from 12.1.0 stable to 13 stable will be easy and smooth.
-
I would love it if the focus was put on going from stable v12 to stable v13, not 13 beta. I have two mods of major importance that no longer work because they were tuned for v13 a/b and now glitch on my stable v12. I don't want to risk updating my site to an alpha or beta flavor. I was advised to wait, which was good advice. However, if mods are being tuned for a version of UNA that is still in development and then put in the Market as an update it causes problems when a site owner who has been exercising caution updates those mods and now has problems with them.
-
That's why I run a development server, setup to receive alpha/beta updates, in order to test and contribute to the error haunting (that is btw the deal for using open source software for absolutely zero), and a production server, that is setup to only receive stable version updates.
-
That is a setup I would love to have one day.
