Hi, there is a way to close a set of issues with a bulk change (without sending an email). I was told when I manually spammed the dev list right before I created my first rc: - bulk change - select issues - select "Transition Issues" - select "Close Issue" - deactivate "Send mail for this update" ;-) - ...
I do not have a strong opinion about it. I just mentioned it because I noticed it while reviewing. Best, Peter Am 26.06.2015 um 15:52 schrieb Marshall Schor: > A while back, people noticed that Jira bulk changes could not be applied to > closed issues, so, a practice of resolving (but not necessarily closing) > issues > has crept into our process, and has been there a while. > > I don't feel strongly one way or another - I tend to tread resolved as "work > is > finished", more or less the same as closed. > > -Marshall > > On 6/26/2015 9:31 AM, Peter Klügl wrote: >> The jira issues for this release are not closed but only resolved. >> >> Best, >> >> Peter >> >> Am 26.06.2015 um 13:38 schrieb Peter Klügl: >>> built current trunk of ruta with staged artifacts - two tests in >>> ruta-core failed: >>> InvisibleWildcardMatchTest.test:41 size of expected annotations (0) does >>> not match with actual size (1). >>> MarkInGreedyComposedTest.testWildCardFollowedByComposedReversed:42 size >>> of expected annotations (2) does not match with actual size (0). >>> >>> I'll investigate it. Most likely it's caused by workarounds introduced >>> for "bugs" in uimaj. >>> >>> Best, >>> >>> Peter >>> >>> Am 26.06.2015 um 12:15 schrieb Peter Klügl: >>>> testing environment: Windows 7 64bit, Java 7 >>>> >>>> compared svn-tag with source-release - OK (only the usual diff and some >>>> .project files) >>>> deleted .m2/../uima, mvn clean install svn-tag - OK >>>> deleted .m2/../uima, mvn clean install source-release - OK >>>> >>>> installed features and tested editor in kepler - OK >>>> installed and tested ruta 2.3.0 - OK (installer complained, but without >>>> reason) >>>> installed features and tested editor in luna - OK >>>> installed and tested ruta 2.3.0 - OK >>>> installed features and tested editor in mars - OK >>>> installed and tested ruta 2.3.0 - OK >>>> The eclipse bundles are not signed. I must admit that I lost the >>>> overview on this. >>>> If you can give me a pointer I could prepare this for the next ruta >>>> release and >>>> we could then integrate it for the next uimaj release, or vice versa. >>>> >>>> more testing will follow... >>>> >>>> Best, >>>> >>>> Peter >>>> >>>> Am 25.06.2015 um 22:39 schrieb Marshall Schor: >>>>> Hi, >>>>> >>>>> I've posted the UIMAJ SDK 2.8.0 rc1 release candidate. >>>>> >>>>> This version has mainly bug fixes, but includes two new things: one is >>>>> the index flattening for sorted indexes, and the other is the improved >>>>> Java Cas view that's part of the document analyzer. >>>>> >>>>> The list of changes in Jira: >>>>> >>>>> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%202.8.0SDK%20AND%20project%20%3D%20UIMA >>>>> >>>>> The source and binary zip/tars and the Eclipse update site are staged to >>>>> http://people.apache.org/~schor/uima-release-candidates/uimaj-2.8.0-rc1/ >>>>> <http://people.apache.org/%7Eschor/uima-release-candidates/uimaj-2.8.0-rc1/> >>>>> >>>>> The Maven artifacts are here: >>>>> https://repository.apache.org/content/repositories/orgapacheuima-1056 >>>>> >>>>> The SVN tags are here: >>>>> http://svn.apache.org/repos/asf/uima/uimaj/tags/uimaj-2.8.0/ >>>>> >>>>> and for the Eclipse Update Site: >>>>> http://people.apache.org/~schor/uima-release-candidates/uimaj-2.8.0-rc1/eclipse-update-site/uimaj/ >>>>> <http://people.apache.org/%7Eschor/uima-release-candidates/uimaj-2.8.0-rc1/eclipse-update-site/uimaj/> >>>>> >>>>> 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. >>>>> >>>>> -Marshall >>>>>
