Author: anonymDate: 2014-10-14 09:57 UTC To: The Tails public development discussion listSubject: Re: [Tails-dev] Migrating to (something closer to) the regular Tor
Browser
14/10/14 00:57, intrigeri wrote:
> anonym wrote (13 Oct 2014 15:54:06 GMT) :
>> Please merge feature/8031-refactor-10-rbb-hook into devel and testing if
>> everything looks good!
>
> Also:
>
> --- a/wiki/src/contribute/release_process/tor-browser.mdwn
> +++ b/wiki/src/contribute/release_process/tor-browser.mdwn
> @@ -4,20 +4,28 @@
>
> Have a look at
>
> -* https://archive.torproject.org/tor-package-archive/torbrowser/
> +* http://archive.torproject.org/tor-package-archive/torbrowser/
> * http://www.torproject.org/dist/torbrowser/
> * http://people.torproject.org/~mikeperry/builds/
> -* https://people.torproject.org/~linus/builds/
> +* http://people.torproject.org/~linus/builds/
>
> I'd rather see the RM use HTTPS, and then explicitly drop the "s" (if
> the limitation is still applicable) in the next step that, I suppose,
> explains why this change was made ("Then update the url to the one
> chosen above").
>
> As a bonus, being explicit about it will avoid seeing the RM
> copy'n'paste from their browser URL bar a HTTPS URL that won't work at
> ISO build time, after being redirected e.g. thanks to HTTPS
> Everywhere :)
Makes sense. I found it easier to automate the release process, see
commit b36270b.
Cheers!