[Tails-dev] Forcing a full upgrade to 1.1: consequences [Was…

Delete this message

Reply to this message
Author: intrigeri
Date:  
To: The Tails public development discussion list
Old-Topics: Re: [Tails-dev] [review'n'merge:1.1] bugfix/looser-memory-requirements-for-upgrades-check (#7235)
Subject: [Tails-dev] Forcing a full upgrade to 1.1: consequences [Was: bugfix/looser-memory-requirements-for-upgrades-check (#7235)]
anonym wrote (19 May 2014 18:28:44 GMT) :
> Not sure if it will matter, but I guess the 1.0_to_1.1{,~rc1} IUKs will
> be huge due to the Wheezy upgrade...


Sure.

My (possibly unwritten) plan has always been to force a full upgrade
to 1.1{,~rc1}: the corresponding IUK would likely be too big to be
practically downloadable + installable (due to download time + RAM +
free space on the system partition needs) for most, if not all, of our
users. And anyway, one cannot pile up IUKs forever on a Tails system
partition, and one has to do a full upgrade from time to time.
Now's time :)

I don't think the release notes need to mention it explicitly, as the
Upgrader already put it clearly enough IMO. However, it might be worth
encouraging people to do a fresh new installation when switching to
1.1, for a few reasons:

1. it forces all users to adjust their system partition's size to our
new standard (2.5 GiB), so we don't have to worry about legacy
sticks anymore;
2. it makes sure all up-to-date sticks have the new UEFI-compatible
partition table (the Installer hasn't been patched to do it on the
fly at upgrade time yet).

Cheers!