Just to clarify, are we talking about splitting the UI and backend into two separate Git repos? If not, I'd propose that is the way to go. That allows us to release each one individually. Not sure the need for NPM packaging though...you'll have to explain that.
On Thu, Jan 29, 2015 at 7:16 AM, Matt Franklin <[email protected]> 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. >
