Note: The goal for this thread is for LMDE 1 users to share information and feedback to help Mint developers provide a seamless update through the normal desktop Update Notifier mechanism. Current users should be able to update LMDE through the normal Update Notifier mechanism. Please stay focused on that as a final goal, although testing to achieve this purpose will include the command line.
Standard disclaimer: Please perform all testing on a spare system or virtual machine and not a production system.
Less experienced users are encouraged to participate because that perspective will help produce a safe and robust update process.
Discussion:
While reaching RC status is happy news
, current LMDE 1 users are concerned with updating existing systems.From LMDE forum and blog comments, updating current LMDE 1 systems has not yet received developer attention and has not been tested. Apparently development and testing will be performed after the ISOs move from RC status to official release.
That time line is not important. New users and current users require different support solutions.
Question: How will current LMDE 1 users be notified about LMDE 2 updates?
Not all LMDE users are propeller-heads. People also are busy and don't always keep abreast of computer news. Users depend upon the Update Notifier to keep systems current.
A grace period for supporting LMDE 1 would be diplomatic and prudent. A notification would be provided through the Update Notifier. Diplomatic in that support for LMDE 1 will end after a specific period (for example, 8 weeks?). During that period only security updates will be provided (Firefox, Thunderbird, Flash, etc.). At the end of the period another notification arrives telling users that LMDE 1 support is ended, no further security updates will be forthcoming, and users are expected to update to LMDE 2 to continue receiving support.
One way or another LMDE 1 users need to be formally notified through the update mechanism. They should be provided time (grace period) to prepare for the updates.
Updating presumptions:
* Repository information is not updated unless the user agrees.
* Users are notified that downloading and updating require a long time.
* The Update Manager updates repo information and then restarts itself.
How the update proceeds thereafter is the purpose of this forum thread.
and I have a 6 Mbps ISP connection. In hindsight I recommend starting the downloads and then cook dinner. I needed somewhere between 45 minutes to an hour to fully download. Note: That is just downloading, not updating the system. 
