[VOTE] Release Apache Rya (Incubating) version 4.0.0 RC1
The Apache Rya community has voted and approved the proposed release of Apache Rya 4.0.0 (Incubating) RC1. We now kindly request the Incubator PMC members review and vote on this incubator release. Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that supports SPARQL queries. Rya is a scalable RDF data management system built on top of Apache Accumulo®. Rya uses novel storage methods, indexing schemes, and query processing techniques that scale to billions of triples across multiple nodes. Rya provides fast and easy access to the data through SPARQL, a conventional query mechanism for RDF data. More information can be found at http://rya.incubator.apache.org/ [VOTE] Thread: https://lists.apache.org/thread.html/e4ac6e5908dd61912d9f6423d6eab794fc07a77db5a3606b583bef60@%3Cdev.rya.apache.org%3E [VOTE][RESULT] Email: https://lists.apache.org/thread.html/a26193173404558eec762a39dd8ab87890c9fd536c37a8f6d1ae0f85@%3Cdev.rya.apache.org%3E The source zip, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/incubator/rya/rya-incubating-4.0.0-rc1/ Ancillary artifacts such as poms, jars, wars, ect. can be found here: https://repository.apache.org/content/repositories/orgapacherya-1011/org/apache/rya/ The Git tag is rya-incubating-4.0.0-rc1 The Git commit ID is 824090ac1b33c3b4ba52bfb8a67abfdc4f0ceea3 https://gitbox.apache.org/repos/asf?p=incubator-rya.git;a=commit;h=824090ac1b33c3b4ba52bfb8a67abfdc4f0ceea3 Checksums of rya-project-4.0.0-source-release.zip: SHA1: e5e91b19abddbdf3c9f0e18469433e730bef7957 MD5: 1d46620a37df803c3ba0b1b383c1da10 Release artifacts are signed with the following key: https://people.apache.org/keys/committer/mihalik.asc KEYS file available here: https://dist.apache.org/repos/dist/release/incubator/rya/KEYS Issues that were closed/resolved for this release are here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319020=12341289 The vote will be open for 72 hours and close at 6:30 PM Thursday, July 25, 2019 (EDT). Please download the release candidate and evaluate the necessary items including checking hashes, signatures, build from source, and test. Then please vote: [ ] +1 Release this package as rya-project-4.0.0 [ ] +0 no opinion [ ] -1 Do not release this package because because...
Re: Board@ subscriptions
Tags might help non-board member. But as a board member, I take care to read every message to board@ and members@ And right now, that is exhausting. On Mon, Jul 22, 2019 at 6:57 AM Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > Hi Tom, > > On Sun, Jul 21, 2019 at 6:38 PM Tom Barber wrote: > > ...Quick protocol question as the board isn’t fit for purpose and I’m > fed up > > of it clogging up my inbox > > Requiring subject line tags like [chairs] on board@ might help > tremendously in keeping the traffic manageable by PMC chairs, if the > convention is that it's the only messages that they have to read. > > If you feel this might help you it might be good to start a [POLL] > thread on board@ so that other PMC chairs can express their interest. > > -Bertrand > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [incubator] branch master updated: Make the automated publishing info more prominent
Thank you Bertrand. Regards, Dave > On Jul 22, 2019, at 7:18 AM, bdelacre...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repository. > > bdelacretaz pushed a commit to branch master > in repository https://gitbox.apache.org/repos/asf/incubator.git > > > The following commit(s) were added to refs/heads/master by this push: > new 18cd6ed Make the automated publishing info more prominent > 18cd6ed is described below > > commit 18cd6ed02552b1217cc329f936ffe75c43ce > Author: Bertrand Delacretaz > AuthorDate: Mon Jul 22 16:18:29 2019 +0200 > >Make the automated publishing info more prominent > --- > README.md | 43 +-- > 1 file changed, 21 insertions(+), 22 deletions(-) > > diff --git a/README.md b/README.md > index 737bce9..df5bd42 100644 > --- a/README.md > +++ b/README.md > @@ -10,6 +10,25 @@ and raise a pull request. > Use the > [general@incubator.a.o](https://lists.apache.org/list.html?general@incubator.apache.org) > mailing list to contact > the Incubator PMC which manages this website. > > +## Automated publishing - Website and Clutch data > + > +Commits to the `master` branch are automatically checked out and built using > `build_site.sh` by the > +[Incubator GIT Site - part > 2](https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20GIT%20Site%20-%20part%202/) > +Jenkins job. The results are pushed to the [`content` folder of the > `asf-site` branch](https://github.com/apache/incubator/tree/asf-site/content) > +which is in turn published automatically to http://incubator.apache.org/ by > the ASF's `gitwcsub` mechanism. > + > +The data for http://incubator.apache.org/clutch/ takes longer to build so it > is handled by a separate > +[SVN Clutch Analysis - part > 1](https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/) > +Jenkins job that runs the `build_clutch.sh` script that's scheduled to run > regularly. The results are stored in the > +[`reserve` folder of the `asf-site` > branch](https://github.com/apache/incubator/tree/asf-site/reserve) > + > +For now that Clutch data is still managed in svn, at > http://svn.apache.org/repos/asf/incubator/public/trunk/ , see > +the build scripts for more info. The projects folder (podling status pages) > and the ip-clearance folders are also still in svn > +and the html is built using `ant docs` in the `build_clutch.sh` script. > + > +Any build failures are reported to > *[cvs@incubator.a.o](https://lists.apache.org/list.html?c...@incubator.apache.org)* > +mailing list. > + > ## Prerequisites for building the website locally > > The website is built using [JBake](https://jbake.org/) and Groovy templates. > @@ -22,7 +41,7 @@ The builds for the website do require internet access. > - `export JBAKE_HOME=/usr/local/Cellar/jbake/2.6.4` > - Ensure that you have a JVM locally, e.g. > [OpenJDK](http://openjdk.java.net/install/) > > -## Building & testing the site > +## Building & testing the site locally > > To test the site locally, use > > @@ -33,7 +52,7 @@ quickly if any changes are made. > > That script can be called with any of the [arguments you would pass to > jbake](https://jbake.org/docs/2.6.4/#bake_command). > > -### Clutch and Legacy SVN Content (careful) > +### Building the Clutch and Legacy SVN Content (if you know what you're > doing) > > **Warning** do not run the clutch build scripts unless you are sure you > understand them, and please be careful not to commit any of the resulting > assets and pages to the git master branch. That content and data is only > committed to the `asf-site` > branch's `reserve`folder as mentioned below. > @@ -41,26 +60,6 @@ branch's `reserve`folder as mentioned below. > The `build_local_clutch.sh` script can be used to build the Clutch data, but > that's updated automatically by the Jenkins > builds as `build_clutch.sh` mentioned below so it's not required unless you > want to test that. > > - > -## Automated builds - website and Clutch data > - > -Commits to the `master` branch are automatically checked out and built using > `build_site.sh` by the > -[Incubator GIT Site - part > 2](https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20GIT%20Site%20-%20part%202/) > -Jenkins job. The results are pushed to the [`content` folder of the > `asf-site` branch](https://github.com/apache/incubator/tree/asf-site/content) > -which is in turn published automatically to http://incubator.apache.org/ by > the ASF's `gitwcsub` mechanism. > - > -The data for http://incubator.apache.org/clutch/ takes longer to build so it > is handled by a separate > -[SVN Clutch Analysis - part > 1](https://builds.apache.org/view/H-L/view/Incubator/job/Incubator%20SVN%20Clutch%20Analysis%20-%20part%201/) > -Jenkins job that runs the `build_clutch.sh` script that's scheduled to run > regularly. The results are stored in the > -[`reserve` folder of
Re: [VOTE][LAZY] the Incubator as a service provider for podlings (was: overzealous bureaucracy...)
On Thu, Jul 18, 2019 at 10:12 AM Bertrand Delacretaz wrote: > ...I'm planning to merge #12 in the next few days unless someone from the > Incubator PMC objects... I have merged that now, thanks for the comments and contributions there, the content is now live at http://incubator.apache.org/ -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[GitHub] [incubator] bdelacretaz merged pull request #12: Rework the homepage as discussed in 'overzealous bureaucracy' thread
bdelacretaz merged pull request #12: Rework the homepage as discussed in 'overzealous bureaucracy' thread URL: https://github.com/apache/incubator/pull/12 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Board@ subscriptions
Hi Tom, On Sun, Jul 21, 2019 at 6:38 PM Tom Barber wrote: > ...Quick protocol question as the board isn’t fit for purpose and I’m fed up > of it clogging up my inbox Requiring subject line tags like [chairs] on board@ might help tremendously in keeping the traffic manageable by PMC chairs, if the convention is that it's the only messages that they have to read. If you feel this might help you it might be good to start a [POLL] thread on board@ so that other PMC chairs can express their interest. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Board@ subscriptions
Not really Ted, but we’re all grown up’s here and I wouldn’t let my 5 and 7 year olds behave like the more vocal members of the board do on both sides of the arguments. I dislike moderation and to behonest, with the changes of the moderation list for board@ part of me wants to argue that in actual fact *no* board or ex-board members should have the ability to moderate because everyones judgement is clouded! But I shall not, as that opens yet another can of worms. I retire from board lurking and life until this mess is sorted out, and I don’t expect that to be any time soon. Tom On 21 July 2019 at 10:44:55, Ted Dunning (ted.dunn...@gmail.com) wrote: Can you make suggestions about what levels of moderation / social enforcement would make the mailing list tolerable for you but (from your understanding) would be acceptable? -- Spicule Limited is registered in England & Wales. Company Number: 09954122. Registered office: First Floor, Telecom House, 125-135 Preston Road, Brighton, England, BN1 6AF. VAT No. 251478891. All engagements are subject to Spicule Terms and Conditions of Business. This email and its contents are intended solely for the individual to whom it is addressed and may contain information that is confidential, privileged or otherwise protected from disclosure, distributing or copying. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Spicule Limited. The company accepts no liability for any damage caused by any virus transmitted by this email. If you have received this message in error, please notify us immediately by reply email before deleting it from your system. Service of legal notice cannot be effected on Spicule Limited by email.
Re: Board@ subscriptions
To make Dave's answer specific to your question: Yes, as chair of Apache Drat (a TLP) you are expected to follow board@ "to ensure that [you] are aware of Foundation level issues that may affect their project": https://www.apache.org/dev/pmc.html#chair Podling or IPMC folk do *not* need to subscribe (and unless they're Members, they can't subscribe to board@). Personally, I expect TLP Chairs to ensure quarterly reports are submitted and that their project replies to all direct board questions (typically the "Board feedback on..." emails) in a timely manner. Reading *all* of the rest board@ is not something I personally think plenty of chairs do, which I certainly understand the past month or so. Ted Dunning wrote on 2019-7-21 1:44PM EDT: > Tom, > > We need to fix board@. You are correct that it isn't usable currently. Not > for you. Not for the board. +1, Ted is spot on. The directors are working on improvements, but need thoughtful ideas and feedback. > Can you make suggestions about what levels of moderation / social > enforcement would make the mailing list tolerable for you but (from your > understanding) would be acceptable? > > > > On Sun, Jul 21, 2019 at 9:37 AM Tom Barber wrote: > >> Hello >> >> Quick protocol question as the board isn’t fit for purpose and I’m fed up >> of it clogging up my inbox. Do incubating project chairs for incubating >> projects have to be subscribed to board@? >> >> If so I’ll start the process of replacing myself as DRAT chair. If not I’ll >> just unsubscribe. >> >> Thanks >> >> Tom -- - Shane Director & Member The Apache Software Foundation - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
