1. svn co
http://svn.apache.org/repos/asf/uima/sandbox/uima-ducc/tags/uima-ducc-1.1.0/
2. mvn clean install -Pbuild-duccdocs
3. followed instructions for (re-)installing live DUCC demo
https://cwiki.apache.org/confluence/display/UIMA/DUCC#DUCC-t2

Looks (mostly) good.  Demo is running here:
http://uima-ducc-demo.apache.org:42133/jobs.jsp

I note the following:

a) the "name problem" reported previously is resolved by specifying the
correct svn co, as Jerry suggests
b) the Job Details page Processes tab seemingly takes a non-trivial amount
of time to initially display and later update; I've not seen this before or
elsewhere - so for now I presume it is a performance problem local to the
demo host.

My (non-binding) vote is: +1 OK to release

Lou.

On Mon, Oct 20, 2014 at 9:52 AM, Jaroslaw Cwiklik <[email protected]> wrote:

> The reason why you get uima-ducc-2.0.0-SNAPSHOT-bin.tar.gz is because you
> checked out from trunk
> instead of RC5 tag. Technically the same code base but the be 100% sure
> just check out from tag and
> redo your testing as we vote on the RC (tag) not whats in the trunk.
>
> Jerry C
>
> On Mon, Oct 20, 2014 at 9:09 AM, Lou DeGenaro <[email protected]>
> wrote:
>
> > 1. svn co https://svn.apache.org/repos/asf/uima/sandbox/uima-ducc/trunk
> .
> > 2. mvn clean install -Pbuild-duccdocs
> > 3. followed instructions for (re-)installing line DUCC demo
> > https://cwiki.apache.org/confluence/display/UIMA/DUCC#DUCC-t2
> >
> > Looks (mostly) good.  Demo is running here:
> > http://uima-ducc-demo.apache.org:42133/jobs.jsp
> >
> > I note the following:
> >
> > a) the name of the produced .gz file in step 1 was:
> > uima-ducc-2.0.0-SNAPSHOT-bin.tar.gz
> > b) the Job Details page Processes tab seemingly takes a non-trivial
> amount
> > of time to initially display and later update; I've not seen this before
> or
> > elsewhere - so for now I presume it is a problem local to the demo host.
> >
> > Lou.
> >
> >
> > On Fri, Oct 17, 2014 at 9:43 AM, Jaroslaw Cwiklik <[email protected]>
> > wrote:
> >
> > > Hi,
> > >
> > > the Apache UIMA DUCC v1.1.0 RC5 is ready for voting.
> > >
> > > DUCC stands for Distributed UIMA Cluster Computing. DUCC is a cluster
> > > management system providing tooling, management, and scheduling
> > facilities
> > > to automate the scale-out of applications written to the UIMA
> framework.
> > > Core UIMA provides a generalized framework for applications that
> process
> > > unstructured information such as human language, but does not provide a
> > > scale-out mechanism. UIMA-AS provides a scale-out mechanism to
> distribute
> > > UIMA pipelines over a cluster of computing resources, but does not
> > provide
> > > job or cluster management of the resources. DUCC defines a formal job
> > model
> > > that closely maps to a standard UIMA pipeline. Around this job model
> DUCC
> > > provides cluster management services to automate the scale-out of UIMA
> > > pipelines over computing clusters.
> > >
> > > There were two issues fixed since RC4
> > >
> > > - Manually generated JIRA report to include in the release. Maven
> changes
> > > plugin only pulls in the first 100 jiras. Ducc 1.1.0  has 189 bugs so
> > about
> > > half were missing.
> > >
> > >  - Minor documentation fixes in ducc book.
> > >
> > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20UIMA%20AND%20fixVersion%20%3D%20%221.1.0-Ducc%22%20ORDER%20BY%20key%20ASC
> > >
> > > The Maven artifacts are here:
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheuima-1040/org/apache/uima/
> > >
> > > The source and binary zip/tars are here:
> > > http://people.apache.org/~cwiklik/releases/uima-ducc/1.1.0/RC5/
> > >
> > > The SVN Tag Checkout:
> > >
> > >
> >
> http://svn.apache.org/repos/asf/uima/sandbox/uima-ducc/tags/uima-ducc-1.1.0/
> > >
> > > See: http://uima.apache.org/testing-builds.html for instructions how
> to
> > > test release candidate.
> > >
> > > Vote open for 72 hours.
> > >
> > > Please vote on release:
> > >
> > > [ ] +1 OK to release
> > > [ ]  0 Don't care
> > > [ ] -1 Not OK to release, because ...
> > >
> > > Thanks.
> > >
> >
>

Reply via email to