Schedule of the migration to Git and Gitlab

Week 1: September 16 to 20, 2019

1. Sep. 16: Activate the wiki on Gitlab.
2. Sep. 17: Announce the migration to SIESTA developers.
3. Sep. 19: Create the legacy SIESTA repository.
4. Sep. 20: Test the Bazaar-to-Git bridge.
5. Sep. 20: Select Launchpad bugs for tentative migrations to Gitlab issues.

Week 2: September 23 to 27, 2019

1. Sep. 23: Populate the reference branches of the official SIESTA repository.
2. Sep. 23: Activate the Bazaar-to-Git bridge.

Week 3: September 30 to October 4, 2019

1. Sep. 30: Schedule migrations for developers ready to go.

Week 4: October 7 to 11, 2019

1. Oct. 7: Schedule migrations for developers ready to go.
2. Oct. 11: Write down instructions for assisted migrations.

Week 4: October 14 to 18, 2019

1. Oct. 17: Migrate branches - Round 0 (volunteers).

Week 5: October 21 to 25, 2019

1. Oct. 21: Make the SIESTA repository and wiki public.
2. Oct. 22: Open a Merge Request (MR) from a selected repository to siesta/master.
3. Oct. 24: Announce the future locking of the main SIESTA branches on Launchpad.
4. Oct. 25: Migrate branches - gonzooznog and linres.
5. Oct. 26: Review completed rounds of migrations.

Week 6: October 28 to 31, 2019

1. Oct. 28: Announce the main SIESTA branches on Launchpad as read-only.
2. Oct. 30: Migrate branches - Round 1.

Week 7: November 4 to 8, 2019

1. Nov. 4: Migrate branches - Round 2 (private branches).
2. Nov. 5: Migrate branches - Round 3 (stale branches).
3. Nov. 6: Stop the bridge with Launchpad.
4. Nov. 7: Publish instructions for late developers.
5. Nov. 8: Set up a basic CI infrastructure to test the main SIESTA branches.

Week 8: November 11 to 15, 2019

1. Nov. 11: Announce the end of fast assisted migrations.
2. Nov. 12: Make the legacy repository read-only.
3. Nov. 13: Publish the legacy repository.