[Pkg-anonymity-tools] torbrowser-launcher in Debian stable [Was: annotated tag debian/0.1.8-1 created (now 1e9ff2c)]

[intrigeri]

Hi,

I don't know what Ulrike's and Holger's plans are regarding 0.1.8.
I assume we could probably get another unblock request, but it seems
to me that we can't sensibly postpone having a discussion with the
release team wrt. what strategy could be applicable to maintain
torbrowser-launcher in Debian stable.

(I couldn't find any such previous discussion, please point me to it
if we've already had it.)

I guess our options are:

1. Track upstream in Jessie
2. Track upstream via the "updates" archive (formerly "volatile")
3. Cherry-pick only required fixes from upstream
4. Drop from Jessie, maintain in backports instead
5. Other options?

Long-term wise, we should probably split the package between code
(that would be frozen in Debian stable) and data (that could be
updated as needed). However, some logic that needs to be updated from
time to time (e.g. alpha/beta detection) lives in the code, so it
would need to be parameterized (e.g. the corresponding regexp), and
the paramaters would need to be extracted from the Python code to some
configuration file that we could put in the data package. It's of
course too late to do that for Jessie, but it would be good to file
a request upstream about it so that we don't realize once Stretch is
frozen that it didn't happen yet :)

Cheers,
-- 
intrigeri