18/11/12 11:42, intrigeri wrote: >> I know a progress bar is planned (I looked around in the ticket), >> but due to my experience above I think it's an absolute must that >> it's implemented before we announce this feature publicly. > > I now agree it's a must before this feature is enabled by default. > > However, I think we should not let the lack of a progress bar prevent > us from publicly asking bold users to try incremental upgrades. > There are many more possible bugs that I'd like to see them discover > by running this code in various situations. Obvious, such a public > call for testing would have to list know issues, such as the lack of > progress report during the download phase. Do we agree on this?
I completely agree. I was talking about the future public announcement of *recommending* the use of incremental updates. > Practically speaking, I'd like to prepare and publish the needed files > for the 0.14->0.15~rc1 incremental update, and publish a dedicated > call for testing in our news section. Or just add instructions to the > existing 0.15~rc1 call for testing, but I doubt it would be read by > many people if done this late. How does this sound? I think it's still worthwhile. Cheers! _______________________________________________ tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev
