UNA 13 issues

What is noticeable is that UNA 13 breaks alot of custom templates. It would have been nice to know this beforehand by the Devs that it could render custom templates useless. Before 13 even with bugs the customization of templates was never an issue. Spending months to customize a template tailored to your site just to find out its obsolete in the next update isn't good. Even waiting until 13 comes out is just delaying having to create a whole new custom template.

I get the frustration, but this is really to be expected with whole number version upgrades to basically ANY platform.

This isn't a UNA-specific issue, when the maintainer updates their application, it's expected of any third-party vendors to also update their modules/products for it to be compatible with the latest version of the core application.

Furthermore, it's really not recommended to upgrade any production site to UNA 13 as it's not ready for production use, less you haven't reviewed their GitHub as of late.

I usually always update during alpha and beta to help test for bugs. UNA does need testers in order to advance the stages. My frustration isn't not knowing there will be bugs which is expected but the amount that accumulated in the second phase. As phases advance there should be less bugs. Also the templates should not be broken. I understand when people say please don't update until a stable version is released. That's fine for live sites. But for us testers we need to let it be know what bugs are there, what's broken, how far broken etc. Stable versions cannot exist until all the bugs are acknowledged and fixed. Since this is an extremely huge update that is taking months it isn't an easy fix for UNA developers to simply go over a couple lines of code to find the issues. People need to know if it's certain modules, custom work, new bugs etc when something is wrong. UNA needs more testers than just their team in order to release stable versions. When phases advance that create more bugs than the previous phase it does become a big issue. Timeline for UNA 13 was already released as were most of the basic packages so links in timeline posts should be working. Also yes mod developers don't need to update their mods until stable version is released but they also need to know at what phase does their modules stop working etc. Since these bugs also effect their mods they need to also pay close attention Since technically we are also letting the developers of the mods know when their mods fail. I don't want mod developers to assume their mods will all work on the stable version of 13 just because nobody spoke up to tell them that it failed at phase 1 or 2.

• I usually always update during alpha and beta to help test for bugs.

Do it on a separate install, make a backup of your production site, host it locally, upgrade and test on UNA 13, never, EVER upgrade a production site to an alpha build of anything.

• UNA does need testers in order to advance the stages.

Read my previous statement.

• My frustration isn't not knowing there will be bugs which is expected but the amount that accumulated in the second phase.

Patch one bug, 99 more pop up, that's the general gist when working in the programming field.

• As phases advance there should be less bugs.

In the perfect world, yes, but that's not our reality. Take Windows for example, to this day, they are still patching out bugs on their "final" product. Be more reasonable with your expectations.

• Also the templates should not be broken.

Yes, they should. As the core applications change, any third party addon, albeit added features, or custom templates, will need to change along with the product. World we live in today, not everything is just HTML and CSS these days.

• But for us testers we need to let it be know what bugs are there, what's broken, how far broken etc.

Changelog would be nice, but this is not needed for testing purposes, ever heard of QA in development pipelines? This just screams entitlement, calm down.

• Stable versions cannot exist until all the bugs are acknowledged and fixed.

Review my statement on the Windows product by Microsoft.

• People need to know if it's certain modules, custom work, new bugs etc when something is wrong.

Then WE need to do our due diligence in testing, properly.

• UNA needs more testers than just their team in order to release stable versions.

Point me in the direction where I or anyone else has stated otherwise.

• When phases advance that create more bugs than the previous phase it does become a big issue.

You're over-exaggerating the issues here, review my "patch 1 bug, 99 more pop up" remark. It's nothing new and has been a "meme" in the programming industry since the dawn of time.

• Also yes mod developers don't need to update their mods until stable version is released but they also need to know at what phase does their modules stop working etc.

No, they do not. UNA does not take responsibility for any third-party product, it is up to the respective devs of said product to maintain their own product to make sure it works. Only thing UNA is responsible for, is maintaining their own product.

• Since these bugs also effect their mods they need to also pay close attention Since technically we are also letting the developers of the mods know when their mods fail.

Read my previous statement.

• I don't want mod developers to assume their mods will all work on the stable version of 13 just because nobody spoke up to tell them that it failed at phase 1 or 2.

I'll repeat, "UNA does not take responsibility for any third-party product, it is up to the respective devs of said product to maintain their own product to make sure it works. Only thing UNA is responsible for, is maintaining their own product."

I've been with Boonex for over 13 years.... All you keep repeating is bugs will happen if you don't like it, it's not new. Also saying third developer mods isn't UNAs problem... uh nobody said it was. I specifically said mod developer need to also pay attention to advice of testers when their mods no longer work during phases. Testers are an important part of creating stable updates. As someone who has been with Boonex for over 13 years I already know what is expected and what isn't. I also know that when people are paying money to maintain their site they do expect for developers to pay attention to bugs. Templates being broken this late in UNA 13 is an issue. It's a big issue. To blow off people's work with ehh it's expected it's your fault etc is ignorant. Also like I said Timeline mod and most basic mods have already been updated to UNA 13 so when I reference those mods please don't say "They will wait until full patch".... They were released as stable mods... so if links no longer work on stable 13 mods then that is a huge issue.

Would ya look at that. @Will Roberts

The biggest thing I do @Will Roberts ?

Just wait til stable is released. I know it's hard brotha. But ruining a up and running site, I learned on last major update from 11 to 12. I jumped the gun and installed (Auto Update was on) literally had to fight through the damage.

It's like buying the first released automobile for the first year. There is ALWAYS issues and problems. It's better to wait for the following year or even later.

Its best to just watch the progression and then update to new version when all is clear for install.

Hope this helps brotha.