Suggestion to Core team Re: upgrades

[davcraiguk]

Hi all,

As always its a bit of a nightmare when a new release comes along especially when there are many Joomla sites to upgrade. There also always seems to be so many extensions that become broke even with a bug fix/security release like 1.0.11. I know this could be due to many reasons, but it is still a real pain.

Usually there are fixes, but they are buried deep in forums or in the bug tracker. Neither place is that easy to find a solution to your broken Exts.

PROPOSAL 1:
Core team set up a section on the site, clear for all to see containing official code fixes, file replacements for that release. Keeping it clear and easy to find.  e.g. 1.0.11 -- the global.php suggested change, admin.mambots.php etc.

PROPOSAL 2:
Self Certification of Extensions. All developers have a vested interest in making their Exts work with the latest releases. For example this time I had to update/patch JCE, securityimages, virtuemart, Joomlatwork SEF patch

Developers could post their Exts and update the 'it works!' flag if they are happy that their ext. works OK. Or maybe an extra tick box for 'it works if you upgrade'

One nice clean list of ticks and not ticks at place that is easy to find off the main site. Not a big job.

What yall think?

[dhuelsmann]

Mode Note: Moving to Sites and Infrastructure - Feedback

[brad]

How about this idea..
Releases are tested and only released when they are problem free

We are aware of the issues that user experience, and are working to refine and solve some of them. Thanks for your suggestions and input.

[davcraiguk]

Hi Brad,
Its not so much the tried and tested bit but when some code has been 'hardened' it makes an Ext. break that worked previously. The core files are one thing and the Exts. another. BTW I see the smileys!

Also the release can be problem free but still Exts. get broken post upgrade.

The question has to be asked where is it made known the crucial fixes for a release? It need to be more accessable rather than a post in a forum. Although I must admit that with 200+ beta testers I was surprised the reason for the mambot patch file was not spotted earlier, but hey thats life.

Also some Exts. do not follow the guidelines fully or they have been inherited from Mambo days with flaws that don't show up until the core is hardened. There are also many exts. that seem to be in perpetual beta or RC's, but that in a way goes part and parcel with the nature of Open Source/GPL type projects.

I still think that an official public list of self certified/self maintained Exts. is the way to go. With many sites to update its a scary time doing the first one as you don't know what will work with the new release and what will not work. Some of these sites are commercial and cannot afford to be down or partially functional - that makes it a serious issue, hence the post.

[eyezberg]

Adding this indicator (icon) to the Extensions site might be a solution?
With a disclaimer (could also be in the img tags title): Developer SELF certified extension.
And an option to globally turn it off for ALL extensions, which you'd do once J! id updated,
then each dev has to come back and re-enable it once they have checked.

[davcraiguk]

Good idea.

Keeping the previous release icon and its status as well as the latest release icon could also be good for those who did not want to upgrade to the latest release immediately.

[ot2sen]

I still think that an official public list of self certified/self maintained Exts. is the way to go. With many sites to update its a scary time doing the first one as you don't know what will work with the new release and what will not work. Some of these sites are commercial and cannot afford to be down or partially functional - that makes it a serious issue, hence the post.

Hi davcraiguk,

The issue about turning register globals emulation off was actually raised by Websmurf even before the release of Joomla! 1.0.11.
In the thread "Components not working with Register Globals Emulation off" there have been compiled a list of extensions not working and fixes for some of them: http://forum.joomla.org/index.php/topic,86525.0.html

*The above mentioned ideas for the Extensions Directory has been noted, and the Editorial Team will discuss if theres any need for this. If the list is no longer than the "Components not working with Register Globals Emulation off" (31 extensions for now) then it probably not will be worth the effort as theres close to 800 extensions listed at the moment. 

[davcraiguk]

If the list is no longer than the "Components not working with Register Globals Emulation off" (31 extensions for now) then it probably not will be worth the effort as theres close to 800 extensions listed at the moment

Its not just the register globals issue. Every release upgrade has caused some element of some 3rd part Exts. to fail and subsequent grief at trying to get it all running again. I am not saying this is a fault of the core but necessary for progress. This is not just because of a one of. In 1.0.11 there was a admin.mambot.php post-patch which is also buried in the forum. The forum is the right place to raise the issues but not a permanant repository for serious fixes.

eyezberg's suggestion is good, without the need of going through 800 exts by valuable core staff, just the once of setup. They would be owner up datable.

Good discussion...keep it going please!

[ot2sen]

Unfortunately the 1.0.11 release had some issues. No one likes this, neither the devs., the testers or the end users 
Known issues 1.0.11 Sunbow: http://forum.joomla.org/index.php/topic,90039.0.html
Im convinced that hard work is done to ensure this wont happen again.

And having a stable release without issues, then for the Joomla! Extensions Directory its really simple: At all times, the extensions listed shall be compatible with latest stable Joomla! release. Otherwise the extension will be unpunlished/deleted.

The register globals issue will be an exception for being unpublished as long its a choise of on/off in Joomla! itself. For this particular issue it would be helpfull if the extension developers clearly indicated in their listing if it was compatible with register globals=off or not.

[eyezberg]

At all times, the extensions listed shall be compatible with latest stable Joomla! release. Otherwise the extension will be unpunlished/deleted.

What is this going to be based on, user reports? Looks like as much works as any other solution.. I don't envy maintainers of extensions..