Project

General

Profile

Feature #9498

Feature #5663: Return to Icedove

Feature #6148: Torbirdy in Debian

Feature #7773: Design and implement migration plan for Claws Mail persistent settings and data

Enable Icedove persistence when Claws Mails persistence was enabled

Added by intrigeri over 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Persistence
Target version:
Start date:
05/29/2015
Due date:
% Done:

100%

Feature Branch:
kytv:feature/5663-return-to-icedove
Type of work:
Code
Blueprint:
Starter:
Affected tool:
Email Client

Description

(like what we did for NM when migrating to Wheezy)

Associated revisions

Revision d6045ce7
Added by anonym over 4 years ago

Merge branch 'feature/5663-return-to-icedove' into devel

Fix-committed: #6151, #9498, #10285, #10332

History

#2 Updated by kytv over 4 years ago

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10

I implemented something which seems to be working.

#3 Updated by kytv over 4 years ago

  • % Done changed from 10 to 40
  • Feature Branch set to kytv:feature/9498-transition-claws-persistence-to-icedove
  • Affected tool set to Email Client

#4 Updated by kytv over 4 years ago

  • Assignee changed from kytv to anonym
  • Target version changed from 246 to Tails_1.7
  • QA Check set to Ready for QA
  • Feature Branch changed from kytv:feature/9498-transition-claws-persistence-to-icedove to kytv:feature/5663-return-to-icedove

#5 Updated by anonym over 4 years ago

  • Assignee changed from anonym to kytv
  • QA Check changed from Ready for QA to Dev Needed

#6 Updated by kytv over 4 years ago

  • QA Check changed from Dev Needed to Ready for QA

#7 Updated by kytv over 4 years ago

  • Assignee changed from kytv to anonym

#8 Updated by intrigeri over 4 years ago

I wonder if we should turn a persistent preset (i.e. something that one can see in the persistent volume assistant) into a manual one. Perhaps we need to have #9499 at the same time as this one? In other words, do we want to do #9498 in 1.7 or in 1.9?

#9 Updated by anonym over 4 years ago

  • Assignee changed from anonym to kytv
  • QA Check changed from Ready for QA to Dev Needed

#10 Updated by anonym over 4 years ago

intrigeri wrote:

I wonder if we should turn a persistent preset (i.e. something that one can see in the persistent volume assistant) into a manual one. Perhaps we need to have #9499 at the same time as this one? In other words, do we want to do #9498 in 1.7 or in 1.9?

I do not think we have to replace it. In 1.7 I think we should have both presets activated (with claws' implying activation of icedove's, i.e. the current situation), plus provide manual steps for cleaning up the claws one. 1.9 can be the last release we link to these instruction (and the migration instructions in general) in the release notes. No code changes needed. At some point we may want to clean up the enabling code from live-persist (we still have code for: Migrate Squeeze-era NetworkManager persistence setting to Wheezy :)).

#11 Updated by anonym over 4 years ago

  • QA Check changed from Dev Needed to Info Needed
  • Type of work changed from Code to Discuss

anonym wrote:

See #6151#note-24.

Actually, what this ticket is about is solved. I suppose what remains is if we actually want it. :)

#12 Updated by sajolida over 4 years ago

I'm not sure we should "replace" one with the one or do to many automated steps here (as this could create misunderstandings or complicated setups during the transition, need cleaning, etc.). Instead what about having both Claws and Icedove in t-p-s until Claws is removed? People should active Icedove or deactive Claws manually as instructured. That's more explicit to the user to the cost of being more noisy on the interface (for a couple of releases only).

Once we're in Tails Jessie, we can maybe automatically remove or delete the persistence line about Claws and warn the user about it (unless we think it's a valid usecase to stick with Claws in Tails Jessie).

#13 Updated by intrigeri over 4 years ago

Instead what about having both Claws and Icedove in t-p-s until Claws is removed? People should active Icedove or deactive Claws manually as instructured.

Sounds good.

Once we're in Tails Jessie, we can maybe automatically remove or delete the persistence line about Claws and warn the user about it

I personally see little value in putting any time into removing that config line, and it implies some work + some risks.

(unless we think it's a valid usecase to stick with Claws in Tails Jessie).

Please, no :)

#14 Updated by anonym over 4 years ago

intrigeri wrote:

Instead what about having both Claws and Icedove in t-p-s until Claws is removed? People should active Icedove or deactive Claws manually as instructured.

Sounds good.

I think we're all agreed then.

Once we're in Tails Jessie, we can maybe automatically remove or delete the persistence line about Claws and warn the user about it

I personally see little value in putting any time into removing that config line, and it implies some work + some risks.

Agreed. Let's put instructions for how to clean this up (once the user has migrated the old Claws stuff, potentially) in the manual instructions.

(unless we think it's a valid usecase to stick with Claws in Tails Jessie).

Please, no :)

Agreed, let's not. So far it's been a bunch of poorly integrated bugs that happens to have emailing capabilities. I do not want to continue supporting it.

#15 Updated by kytv over 4 years ago

  • QA Check changed from Info Needed to Ready for QA

#16 Updated by kytv over 4 years ago

  • Assignee changed from kytv to anonym

#17 Updated by anonym over 4 years ago

  • Status changed from In Progress to 11
  • % Done changed from 40 to 100

#18 Updated by anonym over 4 years ago

  • Assignee deleted (anonym)
  • QA Check changed from Ready for QA to Pass

#19 Updated by sajolida about 4 years ago

  • Type of work changed from Discuss to Code

#20 Updated by anonym about 4 years ago

  • Status changed from 11 to Resolved

Also available in: Atom PDF