rave-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stanton Sievers <ssiev...@apache.org>
Subject Re: Release, Merge & Revamp
Date Thu, 29 Jan 2015 15:59:31 GMT
+1 from me as well.

I'm wondering when it comes to versioning is there a better way to indicate
the split?

Sent from a mobile device. Please forgive brevity or typos.
On Jan 29, 2015 10:55 AM, "Gustavo Monarin" <gustavomonarin@gmail.com>
wrote:

> +1.
>
> I would like to highlight the need of splitting the current api from the
> front end.
>
> I am not sure how easy/viable would be to have a 0.25 mixing the current
> state + the angular work.
>
>
>
> On Thu, Jan 29, 2015 at 3:16 PM, Matt Franklin <m.ben.franklin@gmail.com>
> wrote:
>
> > Once RAVE-1293 is merged, I propose we release 0.24, merge the angular
> > branch into the master branch, revamp the static resource organization to
> > put all of the javascript/html modules into proper npm packaging.
> >
> > With this complete, we can release 0.25 with no major changes, but
> > including some of the angular work.  After 0.25, I propose we push for a
> > hard split of the API and front-end, including driving more modularity
> into
> > the API features.  This will be a longer push, so under this proposal,
> 0.25
> > will remain as the last "stable" release under the old paradigm, with
> > 0.26 + representing a new method of building on the project.
> >
> > Thoughts?  Assuming lazy consensus, I will start the 0.24 release as soon
> > as RAVE-1293 is merged.
> >
>
>
>
> --
>
> Gustavo Monarin de Sousa
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message