I've changed the namespace for all repos marked "official" except for Universal Recommender and is running integration tests on them.
Also, I believe the sbt plugin for pio-build needs to be updated. On Tue, Aug 16, 2016 at 12:50 PM, Pat Ferrel <[email protected]> wrote: > Let me know if anything is missing: https://issues. > apache.org/jira/browse/PIO-24 > > > On Aug 16, 2016, at 12:26 PM, Pat Ferrel <[email protected]> wrote: > > +1 > > > On Aug 16, 2016, at 11:35 AM, Donald Szeto <[email protected]> wrote: > > 1) I’ll volunteer to take a couple templates and put them in their own >> repos if we can get some created. >> > Sure. I believe Chan might have some converted repos as well. > > > >> 2) do we have a gallery page yet? we had a good proposal, is it >> implemented? >> > It's already been merged in develop. Once we release the old template > gallery will become a redirection to the new static page. > > > This is needed only for historical reasons, right? The big blue Template > button will go there directly after release, I assume. > > > >> 3) What templates are worth inclusion? Seems like some of the ALS >> recommender ones are supersets of others do we need them all? >> > We should start with a core set of templates and one or a couple that > focuses on a use case (since they are popular): vanilla, recommendation > (both Scala and Java), similar product, classification, e-commerce, and > text classification. > > > sounds good, that is 7. @chan have you scrubbed any of these? > > > >> 4) do we need “release” of these except through Apache git and Github? >> Since they are all built by users I suspect the normal Apache release >> process can be avoided for them, the full push to maven, binary hosting, >> etc. >> > I vote for maintaining the above set of templates to be at least working > and passing integration tests for the main release. They do not necessarily > go into the final binary distribution, but they should all be tagged and > tested against with every release of PredictionIO. > > > +1 > > > >> 5) We need someone to file Infra Jira’s to get repos. If someone can >> coach me on this I will do it. >> > My guess is we can just file an infrastructure ticket to spawn some > discussion. > > > > Who did the original request for repo? Can someone point me to the Jira, > I’ll take it from there > > >> This might only add a week or so to the release date. If we don’t do it I >> bet it will be much more time spent in support and fixing later. >> > Agree. If we all agree let's make this the final major thing to do before > 0.10.0 release to avoid feature creep. > > > +1, with the possible exception of fixing install.sh https://issues. > apache.org/jira/browse/PIO-22 One option is to remove it from the > release, which I favor, discussion on the jira. > > > >
