Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#14212 closed defect (fixed)

Update ReleaseProcess after #13015 changes

Reported by: boklm Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Keywords: MikePerry201501R, TorBrowserTeam201501R
Cc: gk, mikeperry Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I'm attaching a patch to update the release process after the #13015 changes.

Child Tickets

Attachments (1)

0001-Update-ReleaseProcess-after-13015-changes.patch (974 bytes) - added by boklm 5 years ago.

Download all attachments as: .zip

Change History (5)

comment:1 Changed 5 years ago by boklm

Status: newneeds_review

comment:2 Changed 5 years ago by gk

Looks good to me. Mike while you are at it: we should make sure the blog post gets released *after* the new update related files are in place (and possibly tested). I made the mistake the last time (for the 4.0.2 release) to release the blog post first and then popped an updater issue up...

comment:3 Changed 5 years ago by mikeperry

Resolution: fixed
Status: needs_reviewclosed

Merged this. I think I want to think about moving the blog post though. What sort of updater issue was there? It has been my estimation that it is better for the blog users to see the release first and communicate any serious issues to us *before* we unleash the floodgates and try to update everyone.

comment:4 Changed 5 years ago by gk

The problem was that I messed the updater related thing up (I think it was actually just a problem as that was my first release). IIRC some permissions were wrong or not all files were copied to the correct place. The blog post went live and people were wondering what is up with updating to the new version.

The question is probably where do we expect serious issues popping up. If not with respect to the updater then leaving the things as-is is good. If we can imagine the updating procedure itself could be affected then we should switch: if it is not working for some reason, nobody is harmed and we have time to fix it before the first users are showing up asking (that might take longer now, though, as we remove the support for older versions later in the release process from now on). If it is working, great, let the blog post go live.

I wonder what kind of serious issues you have in mind as we probably don't want to wait, say hours, before we let the user getting updates via our updater. If it is thus just a matter of some minutes would that really help finding those blockers which make a difference (we probably would even not have found the Windows crash bug in the 4.0 version that way)? Hmm... What is Mozilla doing?

Note: See TracTickets for help on using tickets.