I think Andy has the right story here (I must have copied it from someone using Linux). In fact, I did the release candidate on a Mac, a fact which will be reflected in my forthcoming vote.
--- A. Soroka The University of Virginia Library > On Feb 2, 2017, at 5:40 AM, Andy Seaborne <a...@apache.org> wrote: > > The Apache Jenkins installation has Linux slaves. > > There are problems with Windows - there are general problems with temp files > getting left around and Jena uses a lot of temp space so it was not playing > nice with other jobs on those machines. > > There aren't any Mac slaves. > > But Java is portable, right? :-) > > I think the text was copied from a vote call from someone who ran on Linux, > so that test was implicitly done already. > > Andy > > On 01/02/17 21:27, Dick Murray wrote: >> ;-) Nothing implied from me and as I thought re Linux/Dev. Thanks (devs) >> for the work. >> >> On 1 Feb 2017 19:33, "A. Soroka" <aj...@virginia.edu> wrote: >> >>> No, I should say that that exclusion is just a nod to the fact that so >>> many of the Jena devs use Linux that it's just much less of an issue to >>> find Linux testers. Windows seems to be generally the hardest platform to >>> get results for. I certainly didn't intend any more than that, but I copied >>> that list from earlier release vote announcements. (!) >>> >>> But maybe I am missing some history? >>> >>> ajs6f >>> >>>> On Feb 1, 2017, at 2:30 PM, Dick Murray <dandh...@gmail.com> wrote: >>>> >>>> Hi. >>>> >>>> Under checking Windows and Mac OS's are listed but not Linux. Is Jena >>>> assumed to pass? I'mean running Jena 3.2 snapshot on Ubuntu 16.04 and >>>> Centos 7. >>>> >>>> If you haven't broken anything in the snapshot then I vote release. ;-) >>>> >>>> On 1 Feb 2017 16:09, "A. Soroka" <aj...@virginia.edu> wrote: >>>> >>>>> Hello, Jena-folks! >>>>> >>>>> Let's vote on a release of Jena 3.2.0. >>>>> >>>>> Everyone, not just committers, is invited to test and vote. Three +1's >>>>> from PMC members permit a release, but everyone is not just welcome but >>>>> _needed_ to do really good full testing. If a non-committer turns up an >>>>> issue, you can bet I will investigate fast. >>>>> >>>>> This is a distribution of Jena and also of Fuseki 1 and 2. >>>>> >>>>> Versions being released include: Jena @ 3.2.0 (RDF libraries, database >>>>> gear, and utilities), Fuseki 1 @ 1.5.0 and Fuseki 2 @ 2.5.0 (SPARQL >>>>> servers). >>>>> >>>>> Staging repository: >>>>> https://repository.apache.org/content/repositories/orgapachejena-1016/ >>>>> >>>>> Proposed distributions: >>>>> https://dist.apache.org/repos/dist/dev/jena/binaries/ >>>>> >>>>> Keys: >>>>> https://svn.apache.org/repos/asf/jena/dist/KEYS >>>>> >>>>> Git tag: >>>>> jena-3.2.0-rc1 >>>>> 4bdc528c788681b90acf341de0989ca7686bae8c >>>>> https://git-wip-us.apache.org/repos/asf?p=jena.git;a=commit;h= >>>>> 4bdc528c788681b90acf341de0989ca7686bae8c >>>>> >>>>> >>>>> Please vote to approve this release: >>>>> >>>>> [ ] +1 Approve the release >>>>> [ ] 0 Don't care >>>>> [ ] -1 Don't release, because ... >>>>> >>>>> This vote will be open to the end of >>>>> >>>>> Monday, 6 February, 23:59 UTC >>>>> >>>>> Thanks to everyone who can help test and give feedback of every kind! >>>>> >>>>> ajs6f (A. Soroka) >>>>> >>>>> >>>>> Checking needed: >>>>> >>>>> • Does everything work on MS Windows? >>>>> • Does everything work on OS X? >>>>> • Is the GPG signature okay? >>>>> • Is there a source archive? >>>>> • Can the source archive really be built? >>>>> • Is there a correct LICENSE and NOTICE file in each artifact (both >>> source >>>>> and binary artifacts)? >>>>> • Does the NOTICE file contain all necessary attributions? >>>>> • Does the tag in the SCM contain reproducible sources? >>>>> >>>>> >>>>> >>>>> >>>>> >>> >>> >>
