[Cosmo-dev] developer needs for 0.7 server testing

[Jared Rhine]

Ted Leung wrote:
>> What I heard from the meeting was a desire to show people local 
>> changes, possibly even not-checked in.

Travis, who is currently wrapped up in coding, confirmed that what he 
was initially thinking.

So we have a few options it seems:

* Have devs check-in to trunk and have a frequently or on-demand 
trunk-demo (problematic when code not ready for trunk)

* Have devs work in branches and check-in every time they want to demo 
(has all the pros and cons of working in branches)

* Do something like rsync-to-a-server from each dev's local tree. 
Either build the code on the server or push the local jars to the server 
too.  (Perhaps best current option)

* Support external IPs or ports and internal static IPs for developers. 
  (Only works when devs are in the office)

* Have devs do development against a remote filesystem (WebDAV, FUSE, 
etc.  (Only works when devs are connected, and would be a little bit 
slower than local access).

> ...so that we have a tight feedback 
> cycle between the designers and the developers.

This could be supported also by "sit down in person" or VNC-based 
desktop broadcast.  These seem to have annoying limits too.

Not trying to direct conclusions to any particular end; just trying to 
list our currently-known options.  The "demo only checked-in code" vs 
"demo not-yet-checked-in code" seems to be the major branch in the 
decision tree.

-- Jared