Urgent request to NOT update to Joomla! 2.5.26 / 3.3.5

[Matt Thomas]

Due to a bug in the 2.5.26 and 3.3.5 releases, we ask that all users not update until 2.5.27 and 3.3.6 are released, which are due out in a couple of hours.

Thanks for your patience and understanding!

Best,

Matt Thomas

matt.thomas@community.joomla.org

[LyriC JoomliC]

Thank You Matt,

Is it possible to know what is the bug ?

Greets,
Cyril

[Sergio Manzi]

Then, just remove it and don't let anyone upgrade from 3.3.3/3.3.4 to 3.3.4/3.3.5.

Take your time, don't hurry up, let the community at large test a release candidate (call it 3.3.6 or whatever).

This "Skype groups" are worrying me a bit: Who's in? Who's out? How can you get in? Can you be left out? Is this a a little bit like a "secret society"? Where their existence is documented?

Really, I don't want to blame anybody and I have the maximum respect on who is offering his time to the Joomla community, but two fuck-ups in a row (if this is the case) seems to be a little bit too much. We should all take a breath and think what and how has gone wrong.

Best regards and my fullest sympathy to whomever is involved.

smz

--
You received this message because you are subscribed to the Google Groups "Joomla! CMS Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cm...@googlegroups.com.
To post to this group, send email to joomla-...@googlegroups.com.
Visit this group at http://groups.google.com/group/joomla-dev-cms.
For more options, visit https://groups.google.com/d/optout.

[Leo Lammerink]

Why is this not posted in the JBS and why is the JBS not involved in testing?

[Viper]

Again? It's a critical bug or not?

[Youjoomla.com]

14h since and we know nothing. can someone give us more details please.

Best Regards
Dan Casky
Youjoomla Customer Service
1670 Southgate Mill DR NW
Duluth ,GA
30096
-------------------------------
www.youjoomla.com
Professional Joomla Web Design Services

[Nils Rückmann]

15 hours later. Still no information, but 3.3.5 is stays recommended http://www.joomla.org/download.html.
If 3.3.5 breaks things, someone should remove this version.

[in...@yourwebservicesltd.co.uk]

It is already too late for many of my clients as they had already updated their sites first to 3.3.4 and then to 3.3.5, so it will be difficult for them to now revert back to 3.3.3, unless anyone has a good suggestion of the best way to do this?

 

Best regards

John

--

[Hannes Papenberg]

Could you for once stop all the conspiracy theories and all the frantic
cries for help and infos and what not in here? If it were a critical
bug, you would have noticed it. Your site would not be working and all
hell would break loose. Instead its a minor inconvenience that the
updater will not properly work after the update, which will be fixable
pretty easily when the time comes. The people available are working hard
on fixing this and giving you a new release asap. For the time being,
there is no reason to pull the release, since it is still good and onyl
that minor update bug is a problem.

At the same time, please stop accusing the active people of building
conspiracy groups. The Skype chat was never a secret and is open for
everybody. Nothing secret or special is happening there, except that
people communicate a little bit faster than via mails. At the same time,
testing requests are send out to a rather large group of 80+ people, so
please don't bitch around that something was not properly tested because
it was send to "only a handfull of people".

There is no need to revert any installation from 3.3.5 to a lower version.

Hannes

Am 01.10.2014 um 12:26 schrieb in...@yourwebservicesltd.co.uk:
>
> It is already too late for many of my clients as they had already
> updated their sites first to 3.3.4 and then to 3.3.5, so it will be
> difficult for them to now revert back to 3.3.3, unless anyone has a
> good suggestion of the best way to do this?
>
>
>
> Best regards
>
> John
>
>
>
>

> *From:*joomla-...@googlegroups.com
> [mailto:joomla-...@googlegroups.com] *On Behalf Of *Nils Rückmann
> *Sent:* 01 October 2014 11:17
> *To:* joomla-...@googlegroups.com
> *Cc:* youjoo...@gmail.com
> *Subject:* Re: [jcms] Urgent request to NOT update to Joomla! 2.5.26 /

> 3.3.5
>
>
>
> 15 hours later. Still no information, but 3.3.5 is stays recommended
> http://www.joomla.org/download.html.
> If 3.3.5 breaks things, someone should remove this version.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Joomla! CMS Development" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to joomla-dev-cm...@googlegroups.com

> <mailto:joomla-dev-cm...@googlegroups.com>.

> To post to this group, send email to joomla-...@googlegroups.com

> <mailto:joomla-...@googlegroups.com>.

> Visit this group at http://groups.google.com/group/joomla-dev-cms.
> For more options, visit https://groups.google.com/d/optout.
>

> --
> You received this message because you are subscribed to the Google
> Groups "Joomla! CMS Development" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to joomla-dev-cm...@googlegroups.com

> <mailto:joomla-dev-cm...@googlegroups.com>.

> To post to this group, send email to joomla-...@googlegroups.com

> <mailto:joomla-...@googlegroups.com>.

[Matt Thomas]

Hi folks,

I've been away since shortly after sending this. While a full postmortem is being written, I can tell you that:

• This bug affects the ability for 2.5.26 / 3.3.5 sites to use the one-click updater. Affected sites will need to use the install from URL or package methods to update to 2.5.27 / 3.3.6.

• The JBS was not involved as the bug had already been identified, fixed and tested.

• I have asked to have 3.3.5 removed from Joomla.org. When this issue was discovered, the update channels were immediately changed to prevent further sites from updating.

Please keep in mind that we're all volunteers doing the best we can. I know that these situations can be frustrating, I have sites affected  too, but everyone is doing what they can to resolve this quickly and effectively.

Thank you for your patience and understanding.

Best,

Matt Thomas
203.632.9322
http://betweenbrain.com

[Youjoomla.com]

You want to take it easy there Hannes. Read all the posts. PLT made it look like conspiracy.

First urging to update with 2 security fixes, than dont update new release will be out in few hours and now 16h later no info. 

All people were asking is info about it.  If you would have said what you just did  at the beginning no one would post one question. 

To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cm...@googlegroups.com.
To post to this group, send an email to joomla-...@googlegroups.com.

Visit this group at http://groups.google.com/group/joomla-dev-cms.
For more options, visit https://groups.google.com/d/optout.

--

[Sergio Manzi]

Hannes,

No frantic cries, but if a message arrives from a PLT member titled "Urgent request to NOT update to Joomla! 2.5.26 / 3.3.5"  (and no further information), I think you'll understand people will start being worried: What can it be? Is my data at risk of corruption? Is there a major security issue? You know, not all bugs are self-evident...

As far as regards "conspiracy theories", I insist: this "Skype chat" is not documented anywhere (as far as I know, and  I'll be happy to retract if I'm proven wrong). You say it is "open for everybody", but again no indication is given on how to join and when and how these chats are held. Some more info would be really appreciated.

Regards,

Sergio

[Hannes Papenberg]

Rightside second box from the top: http://docs.joomla.org/Portal:Bug_Squad

Am 01.10.2014 um 13:22 schrieb Sergio Manzi:
> Hannes,
>
> No frantic cries, but if a message arrives from a PLT member titled

> "/Urgent request to NOT update to Joomla! 2.5.26 / 3.3.5//"/ (and no

> further information), I think you'll understand people will start
> being worried: What can it be? Is my data at risk of corruption? Is
> there a major security issue? You know, not all bugs are self-evident...
>

> As far as regards "/conspiracy theories/", I insist: this "Skype chat"

> is not documented anywhere (as far as I know, and I'll be happy to

> retract if I'm proven wrong). You say it is "/open for everybody/",

[Matt Thomas]

Sergio,

You are absolutely correct, I should have stated the level of severity of this bug as well as any security implications. For that, I apologize  and will do better next time.

Best,

Matt Thomas
203.632.9322
http://betweenbrain.com

To unsubscribe from this group and stop receiving emails from it, send an email to joomla-dev-cm...@googlegroups.com.
To post to this group, send email to joomla-...@googlegroups.com.

[Michael Babker]

Forgive me if I sound pissed off in this message, the last 36 hours has been stressful enough as it is and I'm really not liking the tone that I've been seeing from pretty much everyone between this channel and other communication mediums.

@Leo - JBS was involved in testing things all afternoon yesterday and into the evening hours (based on US time).  No, there wasn't a mailing list post to JBS, I was using real-time chat channels, including the JBS Skype chat and our leadership chats, to immediately ping anyone who was online and found a large response within those chat channels to test the necessary update paths with the patch we were provided.

"Consipracy Theories and Secret Groups" - Review http://docs.joomla.org/Portal:Bug_Squad - All the chat channels, including the Skype chat are there.

Why Skype versus e-mail?  For what I needed to accomplish yesterday, it was quicker and more efficient to work in a real-time chat environment with others that I knew were immediately present versus blasting e-mails to a mailing list, hoping that people respond to it, and trying to keep folks up-to-date on e-mail consumption.  And the communications were in channels where over 100 people were being kept up-to-date on what was happening, including the entirety of the Joomla Leadership Teams.

Why are yesterday's releases still available?  Simple, they don't bring down sites.  The bug we're advising people to not update for lies in the update component.  Whether we worked to quickly provide a patch for that issue or waited until a regularly scheduled release to provide it wouldn't change the update path, however providing it quicker was IMO a better option as the changeset would be smaller and any risk minimalized.  Yes, we pulled the updates from the update channel; the number of posts where people say they can't update is already going to be asininely high since they won't read any posted documentation on the issue.  At the time we pulled the updates, a combined 30,000 downloads of those packages had been made; the damage is done regardless.

What happened last night?  Simple, burnout.  By the time everything was fully prepared to push, it was somewhere around 2:30 AM GMT and I got urged to sleep things off.

Realize, we're all humans here.  Contrary to popular belief, I too need to rest occasionally and that's exactly what happened last night.

To post to this group, send email to joomla-...@googlegroups.com.

[Cyril Rezé]

Thank you Matt! ;-)

[Sergio Manzi]

@Hannes:
Thanks for pointing me (and everybody else) to the info about the JBS Skype chat: I stand corrected. I also want to make it clear that I find absolutely legit and normal that each working group has its private communication channels.

@Matt:
No problem! Shit happens: I know that by direct and personal experience.

@Michael:
Thanks. Yes, we are all human and nobody (not me for sure!) is accusing you or anybody else of anything. If my tone somehow came through as an accusing one, sorry but this was absolutely not intentional.

Now, if I get it right, it seems there are 30000+ sites that have already upgraded to 3.3.5 and will not receive any more automatic upgrade. Is this correct? If this is the case, how can we get around this issue? Does this also involve 3rd party extensions upgrades (the "Joomla! Extensions Updates Notification" plugin)? If not, can we leverage this to push an update fixing this Catch-22 situation?

smz

[Michael Babker]

The update component will still fetch updates and display the notification, but it will fail on downloading and applying the update.

--

[Webdongle Elgnodbew]

Had 4 sites on 3.3.5 ... three of the sites found and installed the 3.3.6 update ... one failed to open a file to check for updates.  With the three that reported successfully update ... can it be assumed that they updated correctly ?

..

To post to this group, send email to joomla...@googlegroups.com.

Visit this group at http://groups.google.com/group/joomla-dev-cms.
For more options, visit https://groups.google.com/d/optout.

[brian teeman]

If the sites report 3.3.6 in the bottom right then yes