Monitored the behavior of RC3 on a large multi-user cluster for a week and
only found the long user name problem. Validated long user names are
working ok with RC4.

+1 OK to release

On Thu, Mar 15, 2018 at 3:55 PM, Burn Lewis <[email protected]> wrote:

> + downloaded binary & source and checked signatures
> + installed binary on a multi-node cluster and ran a large experiment with
> jobs, services & APs
> + ran the mega-30-min tests on 53 simulated nodes but using UIMA-AS 2.9.0
> to avoid bug in 2.10.2
> + built from source and checked signatures
> ^ ran 1.job etc. on that build
> + spot checked install, readme, release notes, issues fixed, licenses &
> notices
>
> [X] +1 OK to release
>
> On Thu, Mar 15, 2018 at 10:24 AM, Jaroslaw Cwiklik <[email protected]>
> wrote:
>
> > Hi,
> > - Spot checked signatures - OK
> > - Built from source - OK
> > - Issues Fixed report - OK
> > - Spot checked duccbook - OK
> > - Spot checked README, RELEASE_NOTES, NOTICE, LICENSE - OK
> > - Spot checked links in duccmon - OK
> > - Spot checked javadocs API - OK
> > - Ran 1.job, 1.dd.job, 1.error.job - OK
> > - Ran 1.job with --wait_for_completion - OK
> >
> > [X] +1 OK to release
> >
> > Jerry Cwiklik
> >
> > On Thu, Mar 15, 2018 at 10:24 AM, Jaroslaw Cwiklik <[email protected]>
> > wrote:
> >
> > > Ducc does not use Tomcat directly but there is a jar with tomcat
> classes:
> > >
> > > /webserver/lib/apache-jsp/org.mortbay.jasper.apache-jsp-8.0.33.jar
> > >
> > > In that jar file there is a notice file which DUCC NOTICE includes.
> > >
> > > - Jerry
> > >
> > > On Thu, Mar 15, 2018 at 9:10 AM, Lou DeGenaro <[email protected]>
> > > wrote:
> > >
> > >> > Downloaded uima-ducc-2.2.2-bin.tar.gz
> > >> <https://dist.apache.org/repos/dist/dev/uima/uima-ducc/2.2.
> > >> 2/RC4/uima-ducc-2.2.2-bin.tar.gz>
> > >> : OK
> > >>
> > >> > Installed and started Apache DUCC demo
> http://uima-ducc-demo.apache.o
> > >> rg:42133/jobs.jsp :
> > >>    - Jobs, Services, Reservations running : OK
> > >>    - WS
> > >>       - Jobs + Details: OK
> > >>       - Reservations + Details : OK
> > >>       - Services + Details : OK
> > >>       - System Administration, Broker, Classes, Daemons, Machines : OK
> > >>       * System DuccBook : OK
> > >>       - System Viz : OK
> > >>
> > >> > Spot check LICENSE file : OK
> > >>    - note typo:
> > >>       (webserver>navigation
> > >>
> > >> > Check README file : OK
> > >>
> > >> > Spot check NOTICE file: OK
> > >>    - line 225 Apache Tomcat is used?
> > >>
> > >> > Check ReleaseNotes.html : OK
> > >>
> > >> > Spot checked DUCC Book: OK
> > >>    - 19.4-6 are "To be filled in."
> > >>    - system-events.log not documented?
> > >>
> > >> Vote on RC4 = +1
> > >>
> > >> Lou.
> > >>
> > >> On Wed, Mar 14, 2018 at 3:01 PM, Jerry Cwiklik <[email protected]>
> > >> wrote:
> > >>
> > >> > Hi,
> > >> > the UIMA-DUCC 2.2.2 release candidate 4 is ready for voting.
> > >> >
> > >> > This version contains the following fixes since RC3:
> > >> >
> > >> > - Fixed Agent to support long user names (up to 32 chars) when
> > >> collecting
> > >> > node processes
> > >> >
> > >> > The list of changes in Jira:
> > >> > https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%
> > >> > 202.2.2-Ducc%20AND%20project%20%3D%20UIMA
> > >> >
> > >> > The source and binary zip/tars are staged to
> > >> > https://dist.apache.org/repos/dist/dev/uima/uima-ducc/2.2.2/RC4
> > >> >
> > >> > The Maven artifacts are here:
> > >> > https://repository.apache.org/content/repositories/
> orgapacheuima-1190
> > >> >
> > >> > The SVN tags are here:
> > >> > http://svn.apache.org/repos/asf/uima/uima-ducc/tags/uima-
> ducc-2.2.2/
> > >> >
> > >> > See http://uima.apache.org/testing-builds.html for suggestions on
> how
> > >> to
> > >> > test release candidates.
> > >> >
> > >> > Please vote on release:
> > >> >
> > >> > [ ] +1 OK to release
> > >> > [ ] 0   Don't care
> > >> > [ ] -1 Not OK to release, because ...
> > >> >
> > >> > Thanks
> > >> >
> > >> > Jerry Cwiklik
> > >> > Apache UIMA
> > >> >
> > >> > --
> > >> > Jerry Cwiklik
> > >> > Apache UIMA
> > >> >
> > >> >
> > >>
> > >
> > >
> >
>

Reply via email to