You've missed my point(s), most likely because of my previous email
was long winded.

I advocate a rolling release. While keeping APIs stable. BUT only
after core is stripped out, regression tests are in, language bindings
are in their own repo and the API is _nailed down_. Cause you'll be
stuck with it for a long time.
Till then it is considered beta software and not ready for production
systems - other than Grok who'll cut the teeth.

If stabilization forks are the way NuPIC will go, there certainly
won't be "develop-develop" forks. It's not possible to blue red the
community in this binary fashion.

It'll be fun as long as the larger eco-system, NuPIC community and
Grok are in harmony in a chaotic sense.

_______________________________________________
nupic mailing list
[email protected]
http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org

Reply via email to