The graphs here show quite nicely that many of the projects stopped updating at the same time:
https://fisheye6.atlassian.com/browse/?sort=display_name&d=asc&page=3 Cheers, -- Richard > On 29.08.2016, at 17:13, Marshall Schor <m...@schor.com> wrote: > > Richard Eckart de Castilho looked at > https://fisheye6.atlassian.com/changelog/uimaj and observed that recording of > changes seems to have stopped in June 2016 and he says not only for our > project. > > This could be some change in the Apache SVN "hook", or some problem on the > Atlassian side, I guess. > > Did anything change on the Apache side? > > > -Marshall Schor > > On 8/29/2016 10:38 AM, Marshall Schor wrote: >> When we commit a change into SVN we prefix it with the Jira issue, e.g. >> [UIMA-4681]. This *sometimes* seems to result in an automatic update to the >> Jira issue, under a section called "Development", where it shows a hyper link >> labeled, for instance "2 commits", which then takes you a nice view of the >> changes. >> This automatic coupling of svn commits and Jira issues seems very useful. >> >> However, it's becoming quite intermittent, recently. For example: >> >> -it worked for this Jira: https://issues.apache.org/jira/browse/UIMA-4681 >> >> -it failed for this Jira: https://issues.apache.org/jira/browse/UIMA-4685 >> >> Are we doing something incorrect that is causing this? >> If not, can this be improved so that it always (or at least mostly :-) ) >> works? >> >> -Marshall Schor
