[Cosmo-dev] Cosmo release frequency

[Brian Moseley]

On 10/8/07, Jared Rhine <jared at wordzoo.com> wrote:

> Travis and I discussed over lunch some other crazier ideas.  A separate
> front-end and back-end project would allow the front-end to update on a
> faster cycle than the backend.  It would also allow the simulataneous
> production hosting of a hub.chandlerproject.org and
> beta.hub.chandlerproject.org instances pointed at the same Cosmo backend.

i don't think it's that crazy of an idea. that's one of the reasons
i'd like to split the maven uber-project into subprojects. i can
easily imagine releasing cosmo-ui.war on a separate cycle from
cosmo-service-api.war and cosmo-service-impl.war.