Good point (reliable building). An extension of strict semantic versioning
allows an extension like -incubating, this could include a Jira # too so the
full artifact name might be:
org.apache.predictionio-0.10.0-incubating-jira-255 and this would be tagged
jira-255 in either hotfix of master
We should also talk about how we proceed with versioning these patch
releases. We follow semantic versioning, so naturally we could use major
and minor portions for official releases, and the patch portion for
micro-releases / hotfixes. This way, even though Maven artifacts won't be
published to
Pat's link is the best description of the Git development model that
PredictionIO has been using since the beginning. I also support the use of
hotfix branches that will merge into both master and develop branches.
Branching for different sets of external dependencies, in my opinion,
should be
Github user HyukjinKwon closed the pull request at:
https://github.com/apache/incubator-predictionio-sdk-python/pull/16
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and
Github user gongsy945 commented on the issue:
https://github.com/apache/incubator-predictionio/issues/293
unresolved dependency: io.prediction#core_2.10;0.10.0-incubating: not found
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
