Create a mechanism to update the nupic.core dependency from nupic with every push to nupic.core master #590
Comments
I'm backtracking on this. We don't want |
I don't think we want this. The switch to another version of |
really we don't want the above-described behavior? Lot of the tests/apps |
Perhaps validated, but I wouldn't want nupic to auto-switch to using the Matt Taylor On Tue, Feb 4, 2014 at 3:09 PM, breznak notifications@github.com wrote:
|
@rhyolight commented 2 months ago
Is there any updates on this? Observing numenta/nupic.core-legacy#47 and #751, I propose a special travis build for
I can think of some difficulties, such as:
It could be the other way around, a special build triggered by a |
Thanks for your thoughts @utensil. I will think about this today. |
I would be comfortable having nupic automatically point to |
Should now be closed by numenta/nupic.tools#62 . |
Depends on #588, #589.
When the
master
branch is pushed to innupic.core
, thenupic
project must rebuild with the latest source code fromnupic.core
. Essentially, any push tonupic.core
master should trigger a fresh dependency link fromnupic
-->nupic.core
, which should also trigger a new build of Travis-CI.The text was updated successfully, but these errors were encountered: