[CCC DEV] Towards releases

[Matt Jadud]

Well... You know. Those. That I missed somehow.

(O_o)

Cheers,
M
 On Mar 14, 2013 5:46 PM, "Martin Ellis" <ellism88 at gmail.com> wrote:

>
> On Thu, Mar 14, 2013 at 9:26 PM, Matt Jadud <matt at jadud.com> wrote:
>
>> 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.)
>>
>
>
> Which branches are you talking about?  All branches under
> https://projects.cs.kent.ac.uk/projects/kroc/svn/kroc/branches/ are
> already included.
>
> --
> M
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.concurrency.cc/pipermail/developers/attachments/20130314/302f8f6e/attachment.htm>