Skip to content
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

Enable updates #4

Closed
GoogleCodeExporter opened this issue Aug 9, 2015 · 8 comments
Closed

Enable updates #4

GoogleCodeExporter opened this issue Aug 9, 2015 · 8 comments

Comments

@GoogleCodeExporter
Copy link
Contributor

We need to set up update infrastructure. Not decided yet if I will do this with 
Sparkle or the built-in Mozilla updates (pointed to floodgap).

Original issue reported on code.google.com by classi...@floodgap.com on 8 Nov 2010 at 11:34

@GoogleCodeExporter
Copy link
Contributor Author

Initial support will be done simply by directing people to a download URL.

Original comment by classi...@floodgap.com on 9 Nov 2010 at 4:51

@GoogleCodeExporter
Copy link
Contributor Author

Milestone to nextbeta

Original comment by classi...@floodgap.com on 15 Nov 2010 at 4:53

  • Added labels: Milestone-NextBeta
  • Removed labels: Milestone-Release1.0

@GoogleCodeExporter
Copy link
Contributor Author

Initial work complete. Check for Updates now talks to tenfourfox.com for the 
update XML and has tweaks in it to allow for manual updates. This works from 
Check for Updates...; I'll let timer testing burn in overnight.

Original comment by classi...@floodgap.com on 20 Nov 2010 at 5:33

  • Changed state: Started

@GoogleCodeExporter
Copy link
Contributor Author

The timer works, but still tries to make us download patches. Wrote around that 
code also.

Original comment by classi...@floodgap.com on 20 Nov 2010 at 6:33

@GoogleCodeExporter
Copy link
Contributor Author

Bug 599480 kind of screwed us over when I pulled. Backed out, since we use the 
(IMHO more Mac-like) application menu update item. Need to watch for locale and 
missing string issues, but I'll run a test compile to make sure.

Original comment by classi...@floodgap.com on 4 Dec 2010 at 5:01

@GoogleCodeExporter
Copy link
Contributor Author

"Minefield" keeps showing up in the update nag window. We might need to patch 
this out since it's not obeying branding settings.

Original comment by classi...@floodgap.com on 9 Dec 2010 at 4:23

@GoogleCodeExporter
Copy link
Contributor Author

Patched out. Tonight I will test deploy an "update" and see if the G5 catches 
it.

Original comment by classi...@floodgap.com on 15 Dec 2010 at 2:21

@GoogleCodeExporter
Copy link
Contributor Author

Final glitch fix to handle build IDs since we have multiple IDs for multiple 
arches. VERIFIED.

Original comment by classi...@floodgap.com on 15 Dec 2010 at 4:07

  • Changed state: Verified

classilla pushed a commit that referenced this issue Feb 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant