divmod-dev team mailing list archive

[Florent <florent.xicluna@xxxxxxxxx>]

2013/1/4 Jonathan Lange <jml@xxxxxxxxxxxxx>

>
> > Thank you for your feedback on the bug tracker, or on this mailing list.
>
> Three questions:
>
> 1. Will history be preserved?
>
>
Yes, you can verify it in the repository I already published.
https://bugs.launchpad.net/+branch/~divmod-dev/pyflakes/trunk
This is the branch which would become the new trunk.
I've already checked that all the history is here.


> 2. What will happen to branches in-progress?
>
>
I identified 4 branches:
https://code.launchpad.net/~jml/divmod.org/pyflakes-reporter
https://code.launchpad.net/~dobey/divmod.org/pyflakes-less-redef
https://code.launchpad.net/~witsch/divmod.org/Pyflakes
https://code.launchpad.net/~jml/divmod.org/undefined-after-conditional-del

The first one was merged few days ago, so it's not longer an issue.
This was the more significant pending merge. The three others are minor
changes.
I suggest a moratorium on the new merges until the transition is done.
It will make things easier.

Then I will ask on the merge proposals if the author can refresh and
resubmit his branch against the new trunk. If no reply, I'll do it.


> 3. How can we minimize disruption during & around the migration?
>
>
The thing which can minimize disruption is to apply a moratorium on the
merges in Pyflakes/ until the transition is done.

Then when lp:pyflakes is properly set up, we should remove the directory
from the divmod.org repository (see MP attached to the bug), and update the
homepages for Divmod.org and Pyflakes to make clear that all the Pyflakes
stuff is attached to the Pyflakes project in Launchpad (
https://launchpad.net/pyflakes).

These remaining steps do not involve more than 20 minutes of work.
For example, it could be done on Monday 7th at 8 AM (UTC).
Then probably an [Announce] will be sent to "divmod-dev" and "divmod-users"
mailing lists to inform of the split. It can be done few hours later.

-- 
Florent Xicluna