- Built from source using java 8 on linux - OK
- Ran documentAnalyzer from bin - OK
- Built uima-as-v3 (from branch) - OK
- Ran uima-as runRemoteAsychAE - OK
- Spot checked READE, RELEASE_NOTES, LICENSE, NOTICE - OK
- Spot checked signatures - OK
[X] +1 OK to release
On Mon, Nov 26, 2018 at 2:43
Wrapped up into this discussion is an (implicit) choice of a git workflow.
See https://www.atlassian.com/git/tutorials/comparing-workflows
If I had to guess, I'd say that uimaFIT is following the feature branch git
workflow:
https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branc
[
https://issues.apache.org/jira/browse/UIMA-5912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lou DeGenaro resolved UIMA-5912.
Resolution: Not A Problem
This is not an actual problem, but rather user error. I was not looking i
[
https://issues.apache.org/jira/browse/UIMA-5912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lou DeGenaro reassigned UIMA-5912:
--
Assignee: Lou DeGenaro (was: Jerry Cwiklik)
> DUCC Agent must employ ducc_ling to create job's
[
https://issues.apache.org/jira/browse/UIMA-5912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lou DeGenaro updated UIMA-5912:
---
Description:
Presently JD creates log directory and sub-directories as according to
job specificatio
[
https://issues.apache.org/jira/browse/UIMA-5912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lou DeGenaro reassigned UIMA-5912:
--
Assignee: Jerry Cwiklik (was: Lou DeGenaro)
> DUCC Agent must employ ducc_ling to create job's
