hmmm, seems to be (for me). Did you try clearing your browser cache?
On 4/19/2017 9:08 AM, Peter Klügl wrote: > Hi, > > > I noticed that the news for this release is not linked on the front page. > > > Best, > > > Peter > > > Am 04.04.2017 um 20:46 schrieb Marshall Schor: >> The "cannot open api-change-reports" issue is one more place I missed to set >> the >> folder permissions. The file is there on linux, and you can manually set the >> permissions on the folder, and then see things. >> >> I'll put in a Jira for this. >> >> The release passes with 3 + 1 votes: Marshall Schor, Burn Lewis, and Jaroslaw >> Cwiklik >> >> -Marshall >> >> >> On 4/4/2017 2:35 PM, Burn Lewis wrote: >>> - Checked signatures - OK >>> - Spot checked ReleaseNotes, License, Readme, Notice - OK >>> >>>>> But cannot open the api-change reports for uimaj-core >>> uimaj-cpe uimaj-json (unreadable directories) >>> - Ran documentAnalyzer - OK >>> - Installed jars in DUCC (with UIMA-AS 2.9.0) and ran a couple of UIMA & >>> UIMA-AS jobs - OK >>> - Built from source & checked signatures - OK >>> - Installed those jars in DUCC and tested - OK >>> - Tested loading external settings from the class path - OK >>> >>>>> But in the next release should change the syntax to explicitly >>> distinguish file from class path entries >>> - Tested using a setting variable as part of a descriptor import - OK >>> >>>>> But fails with UIMA-AS in the dd2spring preprocessing step. >>> >>> [X] +1 OK to release >>> >
