divmod-dev team mailing list archive

[Jonathan Lange <jml@xxxxxxxxxxxxx>]

On 4 January 2013 16:58, Florent <florent.xicluna@xxxxxxxxx> wrote:
>
> 2013/1/4 Jonathan Lange <jml@xxxxxxxxxxxxx>
>>
>>
>> 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.
...

I've marked my other branch (undefined-after-conditional-del) as
abandoned. It does not need to be migrated.

> 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.
>

This is definitely a good step, but still has the potential to cause
some disruption. In particular, you can't fix local copies of the
authors' branches. You also can't create branches owned by other
people.

I think this disruption is probably worth it, but others might disagree.

>>
>> 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.
>

I think if you sent an email out & did an announcement today, the
earliest reasonable date for the switch would be Monday 14th. That
gives ~dobey and ~witsch a chance to migrate their code themselves
without sabotaging whatever plans they have for this weekend.

Also, looking at the committers over the last 5 years, Jean-Paul is
far & away the most significant contributor. I'd not do this without
getting a green light from him, and would probably also leave a few
days to give other contributors a chance to say something.

jml