[CCC DEV] Towards releases

[Matt Jadud]

On Thu, Mar 14, 2013 at 3:56 PM, Martin Ellis <ellism88 at gmail.com> wrote:

> So... as per claiming commits I think we have two options...
>
>  1) People add the emails I set to their git-hub profiles and we let the
> commits automaticly (or via support) be assigned to their accounts.
>

To do this, I did the following:

1. I clicked on my name in the upper right-hand corner.
2. Clicked on "Edit Your Profile"
3. Clicked on "Emails"
4. Added the missing email address.
5. (Unnecessarily) clicked "verify." (A verify email had already been sent.)
6. Clicked on the link the verification email.
7. PROFIT.

Well, traditionally it's three steps to PROFIT, but the point being that it
was painless.



>  2) People send me an email address they already have assosiated with
> git-hub I rewrite the history again and repush the repositry.
>

We could do this, but it is probably unnecessary. (I wanted to walk through
step one before I made that claim.)

Are there other things we might want to do to this repository before we
were to "move" to it? There are certainly other questions and concerns.

How best to handle branches? Do we export those separately, and then use
git to merge things together? Or, do we do any branch merging/resolution
first, and then move? (The former is easier, in some ways, but I don't know
what makes the most sense.)

Some of the branches can go away, but some have things that I would like to
hold on to. For example, last year a student started working on
library/port of Carl's new scheduler; that code should be brought over. It
could be done either by 1) saving the branch and merging the code, or 2)
merging into the trunk and then re-running. (At that point, we should think
about all of the branches, to save the number of export/import cycles.)

Opinions?

Cheers,
Matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.concurrency.cc/pipermail/developers/attachments/20130314/3da342b1/attachment.htm>