Hi,
anonym wrote (01 Dec 2013 23:51:06 GMT) :
> I'm worried that this may fail several scenarios (and even complete
> features) in the automated test suite. Does the new branding also change
> the icon in the window title? Please see
> features/images/IceweaselRunning.png -- does that part of the new
> Iceweasel/Tor browser still look the same? (Sorry, I don't have time (or
> the bandwidth) to check this myself right now.)
The window titlebar icon doesn't change so I hope it does not break
the test suite. bertagaz will be running it today, so we'll soon know.
> In case the new branding is too different, updating
> features/images/IceweaselRunning.png is a quick fix of course.
Sure. If needed I'll do it as part of fixing regressions brought by
feature/ff24.
>> I guess we could change this by dropping the "Tor Browser's official
>> .mozconfigs" patch. To be honest, I'm a bit reluctant to change this
>> *now* for 0.22 (frozen, will be released in a bit more than a week),
>> and I'm afraid we did not think of this earlier in this release cycle,
>> but I would be happy to fix this for 0.23 if you think it's required.
> It should be noted that our user documentation mentions Iceweasel
> several times so that discrepancy may be a source of use confusion,
> which may warrant a (potentially temporary) change in the user
> documentation. Switching the name to "Tor browser" in 0.22, and then
> back to "Iceweasel" in 0.23 will perhaps also generate some confusion.
> I feel inclined to say that *if* we release 0.22 with the current "Tor
> browser" branding, then we stick with it. Perhaps that'll even be good
> for consistency with Tor's product, whom many Tails users presumably
> have used before trying out Tails? OTOH, maybe the Tor people will
> object since there are differences (-/+ some patches, adblock, etc.)?
>From a general Tails dev perspective I agree with this reasoning.
With my RM hat I'm hoping whatever decision we make results in us not
touching these bits for 0.22.
Cheers!
--
intrigeri
| GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc
| OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc
%20:%0A>%20>%20I'm%20worried%20that%20this%20may%20fail%20several%20scenarios%20(and%20even%20complete%0A>%20>%20features)%20in%20the%20automated%20test%20suite.%20Does%20the%20new%20branding%20also%20change%0A>%20>%20the%20icon%20in%20the%20window%20title?%20Please%20see%0A>%20>%20features/images/IceweaselRunning.png%20--%20does%20that%20part%20of%20the%20new%0A>%20>%20Iceweasel/Tor%20browser%20still%20look%20the%20same?%20(Sorry,%20I%20don't%20have%20time%20(or%0A>%20>%20the%20bandwidth)%20to%20check%20this%20myself%20right%20now.)%0A>%20%0A>%20The%20window%20titlebar%20icon%20doesn't%20change%20so%20I%20hope%20it%20does%20not%20break%0A>%20the%20test%20suite.%20bertagaz%20will%20be%20running%20it%20today,%20so%20we'll%20soon%20know.%0A>%20%0A>%20>%20In%20case%20the%20new%20branding%20is%20too%20different,%20updating%0A>%20>%20features/images/IceweaselRunning.png%20is%20a%20quick%20fix%20of%20course.%0A>%20%0A>%20Sure.%20If%20needed%20I'll%20do%20it%20as%20part%20of%20fixing%20regressions%20brought%20by%0A>%20feature/ff24.%0A>%20%0A>%20>>%20I%20guess%20we%20could%20change%20this%20by%20dropping%20the%20%22Tor%20Browser's%20official%0A>%20>>%20.mozconfigs%22%20patch.%20To%20be%20honest,%20I'm%20a%20bit%20reluctant%20to%20change%20this%0A>%20>>%20*now*%20for%200.22%20(frozen,%20will%20be%20released%20in%20a%20bit%20more%20than%20a%20week),%0A>%20>>%20and%20I'm%20afraid%20we%20did%20not%20think%20of%20this%20earlier%20in%20this%20release%20cycle,%0A>%20>>%20but%20I%20would%20be%20happy%20to%20fix%20this%20for%200.23%20if%20you%20think%20it's%20required.%0A>%20%0A>%20>%20It%20should%20be%20noted%20that%20our%20user%20documentation%20mentions%20Iceweasel%0A>%20>%20several%20times%20so%20that%20discrepancy%20may%20be%20a%20source%20of%20use%20confusion,%0A>%20>%20which%20may%20warrant%20a%20(potentially%20temporary)%20change%20in%20the%20user%0A>%20>%20documentation.%20Switching%20the%20name%20to%20%22Tor%20browser%22%20in%200.22,%20and%20then%0A>%20>%20back%20to%20%22Iceweasel%22%20in%200.23%20will%20perhaps%20also%20generate%20some%20confusion.%0A>%20%0A>%20>%20I%20feel%20inclined%20to%20say%20that%20*if*%20we%20release%200.22%20with%20the%20current%20%22Tor%0A>%20>%20browser%22%20branding,%20then%20we%20stick%20with%20it.%20Perhaps%20that'll%20even%20be%20good%0A>%20>%20for%20consistency%20with%20Tor's%20product,%20whom%20many%20Tails%20users%20presumably%0A>%20>%20have%20used%20before%20trying%20out%20Tails?%20OTOH,%20maybe%20the%20Tor%20people%20will%0A>%20>%20object%20since%20there%20are%20differences%20(-/+%20some%20patches,%20adblock,%20etc.)?%0A>%20%0A>%20>From%20a%20general%20Tails%20dev%20perspective%20I%20agree%20with%20this%20reasoning.%0A>%20With%20my%20RM%20hat%20I'm%20hoping%20whatever%20decision%20we%20make%20results%20in%20us%20not%0A>%20touching%20these%20bits%20for%200.22.%0A>%20%0A>%20Cheers!%0A>%20--%20%0A>%20%20%20intrigeri%0A>%20%20%20%7C%20GnuPG%20key%20@%20https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc%0A>%20%20%20%7C%20OTR%20fingerprint%20@%20https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc%0A>%20%0A>%20 "Nachricht beantworten")