New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ANNOUNCEMENT: Changes to Updates #29

Closed
andryou opened this Issue Jun 6, 2016 · 6 comments

Comments

Projects
None yet
4 participants
@andryou
Owner

andryou commented Jun 6, 2016

I just wanted to make an announcement regarding updates:

  • Apology: I apologize for the frequency of updates over the past week. Major updates were made to key parts of ScriptSafe, bugs were found (some very critical), leading to subsequent fixes being pushed out. This led to the number of updates being pushed out.
    • A lot has been accomplished in the past week in terms of features and optimizations (such as added regex matching support, hotkey support, WebRTC protection)
    • I thank everyone for your patience and for sticking around. I do hope you notice a significant performance improvement in your browsing experience.
  • Respect Same-Domain Issue (#25): this is one of the bigger issues that I addressed in an update (v1.0.7.8) I uploaded to the Chrome Web Store at 8:45pm eastern yesterday (Sunday, June 5). Ever since it has been in a "Pending Review" status, meaning someone at Google needs to manually approve it before it is pushed out to users. I've just contacted the Chrome Web Store to inquire about the review status and that it is quite an important update. v1.0.7.8 was manually approved and published 26 hours later by Google.
  • Constructive Criticism: I appreciate constructive criticism (and do take them seriously and try my best to improve ScriptSafe, as you can see from submitted issues here). Denouncing my work is not constructive or meaningful. If you're not happy with ScriptSafe, you're free to uninstall it.

Moving forward, you can expect the following:

  • More updates being grouped together, and updates being pushed out when a good amount of fixes has been accumulated (exception: if any are critical fixes)
  • Less critical issues experienced
  • Less frequent updates

Thanks.

@chrcoluk

This comment has been minimized.

Show comment
Hide comment
@chrcoluk

chrcoluk Jun 6, 2016

I am guessing sods law has struck here, with this urgent update been slower than usual for the webstore to update.

End of the day you do this for free, and I respect that hence there is no justification for people been rude to you, the error happened, but you have already said you will react in future to lower the chances of it again. this is good :)

So thank you for this excellent extension and yes the browser does feel faster to use now.

chrcoluk commented Jun 6, 2016

I am guessing sods law has struck here, with this urgent update been slower than usual for the webstore to update.

End of the day you do this for free, and I respect that hence there is no justification for people been rude to you, the error happened, but you have already said you will react in future to lower the chances of it again. this is good :)

So thank you for this excellent extension and yes the browser does feel faster to use now.

@andryou

This comment has been minimized.

Show comment
Hide comment
@andryou

andryou Jun 7, 2016

Owner

@chrcoluk I appreciate it!

Everyone, as promised I will be pushing updates to the Chrome Web Store much less frequently. This repository will always have the latest code updates and can be downloaded/synced at any time. It can be considered to be stable as whatever is synced on here is what I'm personally running.

But if you still want to disable the update notifications, here are steps:

  1. Restart Chrome (required in order for ScriptSafe to update to the latest version, which at this point in time is v1.0.7.8)
    • Previously ScriptSafe would automatically update itself causing any session settings to be lost without any warning
    • In recent updates, the update behaviour was changed so that it would notify users that an update is available and wait for the browser to be restarted
  2. Go to the ScriptSafe options page
  3. Untick Show Update Notification

Note: if you disable this option ScriptSafe will still wait for a complete browser restart before updating itself (to not interrupt your current browsing session). By disabling the above option, you won't know whether or not there's an update for ScriptSafe available.

Owner

andryou commented Jun 7, 2016

@chrcoluk I appreciate it!

Everyone, as promised I will be pushing updates to the Chrome Web Store much less frequently. This repository will always have the latest code updates and can be downloaded/synced at any time. It can be considered to be stable as whatever is synced on here is what I'm personally running.

But if you still want to disable the update notifications, here are steps:

  1. Restart Chrome (required in order for ScriptSafe to update to the latest version, which at this point in time is v1.0.7.8)
    • Previously ScriptSafe would automatically update itself causing any session settings to be lost without any warning
    • In recent updates, the update behaviour was changed so that it would notify users that an update is available and wait for the browser to be restarted
  2. Go to the ScriptSafe options page
  3. Untick Show Update Notification

Note: if you disable this option ScriptSafe will still wait for a complete browser restart before updating itself (to not interrupt your current browsing session). By disabling the above option, you won't know whether or not there's an update for ScriptSafe available.

@andryou

This comment has been minimized.

Show comment
Hide comment
@andryou

andryou Jun 12, 2016

Owner

From this point on I will be posting beta releases here for testing and feedback before pushing them to the Chrome Web Store.

v1.0.7.11 beta is available for testing: more info here - #40

Owner

andryou commented Jun 12, 2016

From this point on I will be posting beta releases here for testing and feedback before pushing them to the Chrome Web Store.

v1.0.7.11 beta is available for testing: more info here - #40

@Sebb767

This comment has been minimized.

Show comment
Hide comment
@Sebb767

Sebb767 Jun 12, 2016

Thanks for all the work!

Sebb767 commented Jun 12, 2016

Thanks for all the work!

@klepas

This comment has been minimized.

Show comment
Hide comment
@klepas

klepas Jun 13, 2016

Thanks Andrew for ScriptSafe and for the dedication to your users.

klepas commented Jun 13, 2016

Thanks Andrew for ScriptSafe and for the dedication to your users.

@andryou

This comment has been minimized.

Show comment
Hide comment
@andryou

andryou Jun 14, 2016

Owner

The update notification was completely removed in v1.0.7.11 and I feel things are stable in v1.0.7.12 (which addressed two important issues and was tested + confirmed by the issue reporters).

Development will continue here, and updates (most likely just enhancements) will be pushed to the Web Store when needed/well-tested.

We've come a long way; I realize there were a lot of releases over the two weeks and just wanted to again thank everyone for sticking around and using ScriptSafe :)

Owner

andryou commented Jun 14, 2016

The update notification was completely removed in v1.0.7.11 and I feel things are stable in v1.0.7.12 (which addressed two important issues and was tested + confirmed by the issue reporters).

Development will continue here, and updates (most likely just enhancements) will be pushed to the Web Store when needed/well-tested.

We've come a long way; I realize there were a lot of releases over the two weeks and just wanted to again thank everyone for sticking around and using ScriptSafe :)

@andryou andryou closed this Jun 14, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment