Discussion about Joomla! 1.0.6 Release

[wroxbox]

The "stable" releases should be betareleases and after two days of client installation testing in production environment the could be a "stable release" .. After all bugs are fixed .. This upgrades have been total crap as Phil said..

[T-Dawg]

for 1.0.5 to 1.0.6 patch file, there is nothing that upgrades version #, so it still reads as 1.0.5.

Hrm... I did .5 to .6 too but it bumped my version number fine

[pcigre]

Please pull donw packages untill this is fixed. People can have serious problems, this is a first priority bug...

[PhilTaylor-Prazgod]

The "stable" releases should be betareleases and after two days of client installation testing in production environment the could be a "stable release" .. After all bugs are fixed .. This upgrades have been total crap as Phil said..

I read on the official site that this release HAS BEEN sent to a few select people a few days ago for testing privatly before the main release - amazing.

[rjs]

The quality just gets worse....

Hey Phil, you are losing me here. You feel the quality of joomla! 1.0.6 is worse than 1.0.5? If so, how? Just the issues with the zip? I'm lost here, try posting whole thoughts when you post. Thanks Phil. I'm not seeing anything in this thread that would warrent your remarks thus far. Just my opinion.

[T-Dawg]

Referring to quality of QA as to "stable" versions of Joomla RE: the rest of this thread

[PhilTaylor-Prazgod]

The quality of the release process and testing of a release before public can access it

I just sent an email to almost 7000 people/customers saying Joomla 1.0.6 was available - and then its not and then it is but its got a huge bug in it

How frustrated would you be to put your own credibility on the line....

[pcigre]

The quality just gets worse....

Hey Phil, you are losing me here. You feel the quality of joomla! 1.0.6 is worse than 1.0.5? If so, how? Just the issues with the zip? I'm lost here, try posting whole thoughts when you post. Thanks Phil.

No it's not zip problem... it's coz
http://forum.joomla.org/index.php/topic,30559.0.html
http://forge.joomla.org/sf/go/artf3072?nav=1

[rjs]

Referring to quality of QA as to "stable" versions of Joomla RE: the rest of this thread

I've read it. I see the issues, but the remarks still go unwarranted. Uless of course you could provide me with information that proved 1.0.6 is causing total dismay and crashing servers.

[Manoxtra]

O my god, did I just blow up my site... after upgrading and saving the config file [ I wanted to open up the site for new registrations ] everybody is locked out, even when I go back to 1.05  I cant login anymore  ???  :'( 

[pcigre]

O my god, did I just blow up my site... after upgrading and saving the config file [ I wanted to open up the site for new registrations ] everybody is locked out, even when I go back to 1.05  I cant login anymore  ???  :'( 

You need to edit manualy the file configuration.php

this line:

Code: Select all

$mosConfig_password = 'yourdatabasepassword';

If you don't know whats your databasepasword, you can change it from phpmyadmin, or you can find it in your backup if you have it.

[neilius]

The database password is not saved in the config file after any change to the global config settings in the admin interface - $mosConfig_password keeps getting cleared.

[PhilTaylor-Prazgod]

I've read it. I see the issues, but the remarks still go unwarranted. Uless of course you could provide me with information that proved 1.0.6 is causing total dismay and crashing servers.

The remarks are not unwarrented.  This release has been plagued with problems that Prior Planning, Testing and preparation could have taken care of.  They are not big issues like causing big security holes and the like - but to people that have not got a large understanding of systems (probably most joomla users) having a site crash on config save is a big issue for them - bigger than you imagine,

Remember that you, Rjs, and I know what we are doing - but many people would not have a clue where to start debugging these problems.

It is clear to me, and others in this tread, the the planning, testing and preparation of this release has been crap. (For goodness sake did no one actually unzip the zip file ad test te zip was not corrupt before uploading it? If they did they would have spotted the extra directories!)

[rjs]

Okay Phil.

[stingrey]

Bug is confirmed and 1.0.7 is being released immediately to correct.


My fault totally on both counts.
I introduced the bug in attempting to improve security.

It was introduced after the Beta was released to testers.


All I can say is that I publicly apologize and am squarely to blame for this.

[PhilTaylor-Prazgod]

hehe - Im not out to blame anyone :-) :-)
But it does highlight my point, that changes should not be made to releases after it has been tested :-) :-)

Sorry for the outburst - but now I have to suck eggs and tell customers its 1.0.7 coming their way and not 1.0.6

[pcigre]

@stingrey : all of us know how much you did for Joomla... So I hope that there aren't many people that updated their live sites...

[Manoxtra]

Thx, my fellow-joomla friends 

Ive gone back to 1.0.5 .... will wait for a better release... 

Phill, what do you mean EXTRA directories? Is this release faulty cause of that or the save password bug in the config file, or maybe both?

[BillyS]

With all due respect to those complainers, I always place these upgrades on a test server before putting into production.  That's just good practice.  This is open source software with good folks dedicated to improving the product.  Reporting bugs is important, throwing stones is just plain ungrateful.

[neilius]

Thankyou stingrey for keeping us informed. Nobody's perfect!

Regards,

Neil.

[Manoxtra]

With all due respect to those complainers, I always place these upgrades on a test server before putting into production.  That's just good practice.  This is open source software with good folks dedicated to improving the product.  Reporting bugs is important, throwing stones is just plain ungrateful.

Hmm, I did not complain or blaim anyone, I was just blown away by this event... sorry for that ... I still am very gratefull for what the devs are doing!!! Joomla is still the BOMB for me, hehe 

[stingrey]

http://forum.joomla.org/index.php/topic ... #msg173432

[stingrey]

hehe - Im not out to blame anyone :-) :-)
But it does highlight my point, that changes should not be made to releases after it has been tested :-) :-)

Sorry for the outburst - but now I have to suck eggs and tell customers its 1.0.7 coming their way and not 1.0.6

No you were within your rights It was warranted and obviously shows why one should stick to proper testing release policies.

[hannma]

Thanks for information Stingrey!

[PhilTaylor-Prazgod]

Hey Im not ungrateful at all - to suggest such a thing is silly - those that know me know I fully support the Core Dev Team

Stingrey knows me well (I think) and Iknow he has an important role to play in the smooth running of Joomla. However proceedures and established practices, when deviated from, cause issues,

while composing this post I see Stingrey has said the same thing in a different way :-)

So looking forward to 1.0.7 now :-) :-) :-)

[neilius]

I feel I must take the opourtunity to highlight this point: I'm sure if we were using a commercial, closed source piece of software that was released with such a bug, it wouldn't be fixed within a couple of hours with the developers keeping their users informed in the same way that stingrey has!

Regards,

Neil.

[Tonie]

Ok, everybody had their say. It happened, and it is going to get fixed soon. Let's leave it at that.

I know why I wasn't hit by this, configuration.php not writable for Apache user......

[jmc]

Rey -
It takes a BIG man to stand up and say unequivocally "It was me!".
Respect to ya! You put the "Open" into Open Source, buddy.
John Mc

[neilius]

I see a package appearing on the Forge!!!!!!!

[chay]

Stingray.  I tip my hat to you again. You're much appreciated.