Considering we are limited in movement right now I won't be able to do an emergency release until April :(

Please pull the release and provide a way for people to downgrade if you can't release till 2 weeks. If you don't, there will be plenty of people that will uninstall the plugin and might not ever reinstall it.

@jmgurney It may be an option (if it will indeed cause uninstalls), but that means other important things will get rolled back. Also it would need to be approved by EFF staff.

Please pull the release and provide a way for people to downgrade if you can't release till 2 weeks. If you don't, there will be plenty of people that will uninstall the plugin and might not ever reinstall it.

@jmgurney We have previous extensions releases on our page to download: https://www.eff.org/https-everywhere. Also, we are in the middle of a very serious pandemic. In normal circumstances, I'd be able to do this today. So I hope patience and grace would be considered.

Please pull the release and provide a way for people to downgrade if you can't release till 2 weeks. If you don't, there will be plenty of people that will uninstall the plugin and might not ever reinstall it.

@jmgurney We have previous extensions releases on our page to download: https://www.eff.org/https-everywhere. Also, we are in the middle of a very serious pandemic. In normal circumstances, I'd be able to do this today. So I hope patience and grace would be considered.

Thank you for the link to the past releases to make things functional. Installing 2019.11.7 makes things functional again. You might want to advertise this and figure out how to stop having people automatically upgraded to 2020.3.16. If the original bug has this work around, I would have used it sooner.

I will be attaching this work around to the bug as well.

There are lots of government websites, like large parts of Alameda County's website that do not have https functional, so blocking people from those websites is not a good outcome, especially in the middle of a crisis like this.

There are lots of government websites, like large parts of Alameda County's website that do not have https functional, so blocking people from those websites is not a good outcome, especially in the middle of a crisis like this.

@jmgurney Right now the more immediate work-around would be to turn EASE mode off for these sites. I understand that this is an urgent issue, but this crisis also affects the real people on this project as well. Hence mistakes and issues occurring due to the added stress on everyone. I could not predict that city actions would happen so quickly I could not come in to do secure patch releases.

To shed some transparency, we have to do this release securely on site. Not remotely. Which should answer why I can not do a release at the moment.

@zoracon Can William (Hainish) do that?

@zoracon Can William (Hainish) do that?

@pipboy96 Due to the Shelter-in-place order by the area, none of us can.

@pipboy96 @jmgurney the entire bay area is under a shelter in place order right now. No one at EFF is available to make a release since it requires coming to the office. You two could help us best by commenting on the bug report instructing people on how to downgrade if they are concerned about the issues in this PR. We currently don't know when we will be able to make a new release of any of our projects. Thank you for your patience with us.

I understand that things take time, but you do have to realize that you said:

Considering we are limited in movement right now I won't be able to do an emergency release until April :(

and there were no workarounds documented, nor statements about any other possible actions to be taken in the near future. Two weeks is a LONG time to leave something broken w/o action or a documented work around. If you had communicated a time line, or simply said we are exploring options, give me a day or two, that would have been helpful.

I understand that things take time, but you do have to realize that you said:

Considering we are limited in movement right now I won't be able to do an emergency release until April :(

and there were no workarounds documented, nor statements about any other possible actions to be taken in the near future. Two weeks is a LONG time to leave something broken w/o action or a documented work around. If you had communicated a time line, or simply said we are exploring options, give me a day or two, that would have been helpful.

@jmgurney It's not just about things taking time, unprecedented events occurred. Where I truly thought we could handle issues that arose from this release. You're right, two weeks is a long time. This was not planned.

We can post and pin an issue. I also planned to communicate this on our social and email channels. Either way, we can't do a release. I am not sure how many ways we can convey this. This is merged in now and that is all that can be done.

@jmgurney The problem is releasing updates is not as simple as pushing a .crx file to a server, there are protections against pushing malicious updates, it's physically impossible to do that outside EFF's office, so until quarantine is lifted we are stuck with a broken release. I hope this explains things better.

And to clarify why the conversation is locked, the issue has a patch in master, I have pinned the issue to the repo involved, and we have discussed in depth with as much calm as possible why a release can't occur.

It should be somewhat obvious that a shelter-in-place order means these are trying and extreme constraints we normally don't have. So this was locked so that we can discuss, resolve, and move forward with the energy I have to give towards this project. There's just not many options for locked conversation categories. So "too heated" was the only one that made the most sense.

@zoracon I thought "Resolved" would be a better reason, but I don't think it matters much. Also, for some reason I don't get this update on Firefox. Was it pulled?

@pipboy96 No it was not pulled, maybe it didn't auto update?