[CCC DEV] Towards releases

[Matt Jadud]

I browsed around, and it looks like a number of people "claimed" their
email addresses since this thread went live. Unless there are objections,
I'd like to see us move to the Git repository for coordination. Over time,
we can do some trimming/pruning of branches, etc.

I used to have huge, lofty goals. Now, I would just like to be able to
build releases for each platform again. I have a Windows VM, and started
running the build scripts. (Of course, software they download no longer
exists, etc., but I'll get there... unless someone else is more of a
Windows wiz than me, and wants to be in charge of Windows builds.)
Likewise, getting the Mac build running again, and ultimately, having a
JEdit package for Linux would be a good thing. (We've never done that.)

All of that said, I wonder if we should look at something like this:

http://codebender.cc/

Either way, my goal is to get the tree "living" again, so that when we do
things that are interesting (or develop a new library for a platform, or
hack a new platform in (R-Pi, for example)) we can actually *ship* them.
Or, for myself, get students using them in projects.

I have two students who have built two new airplanes, and this summer have
four students who will be developing a suite of home energy/environment
monitors. If we get the tree alive again, I can start looking at putting a
grant together that mirrors/supports work back at the Kent mothership.
Unfortunately, it's hard to do that when I can't easily involve students in
projects on the embedded platforms.

Hm. That was longer than intended, and kinda off-thread.

Cheers,
Matt



On Sun, Mar 24, 2013 at 12:29 PM, Martin Ellis <ellism88 at gmail.com> wrote:

> Hi all,
>
> Are we happy with the git repo now?
> What's the next step?
>
> --
> M
>
>
> On Thu, Mar 14, 2013 at 11:31 PM, Matt Jadud <matt at jadud.com> wrote:
>
>> 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/20130324/ff7bc90d/attachment.htm>