Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C5F1E200CC8 for ; Fri, 14 Jul 2017 13:19:29 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C466D16D937; Fri, 14 Jul 2017 11:19:29 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 15B0316D936 for ; Fri, 14 Jul 2017 13:19:28 +0200 (CEST) Received: (qmail 89264 invoked by uid 500); 14 Jul 2017 11:19:28 -0000 Mailing-List: contact dev-help@polygene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@polygene.apache.org Delivered-To: mailing list dev@polygene.apache.org Received: (qmail 89253 invoked by uid 99); 14 Jul 2017 11:19:27 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Jul 2017 11:19:27 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 6A863180706 for ; Fri, 14 Jul 2017 11:19:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.772 X-Spam-Level: X-Spam-Status: No, score=0.772 tagged_above=-999 required=6.31 tests=[KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id KJUNRt0iDV2X for ; Fri, 14 Jul 2017 11:19:25 +0000 (UTC) Received: from relay5-d.mail.gandi.net (relay5-d.mail.gandi.net [217.70.183.197]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 266F25F238 for ; Fri, 14 Jul 2017 11:19:25 +0000 (UTC) Received: from mfilter14-d.gandi.net (mfilter14-d.gandi.net [217.70.178.142]) by relay5-d.mail.gandi.net (Postfix) with ESMTP id D94FF41C087 for ; Fri, 14 Jul 2017 13:19:17 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter14-d.gandi.net Received: from relay5-d.mail.gandi.net ([IPv6:::ffff:217.70.183.197]) by mfilter14-d.gandi.net (mfilter14-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id nRelRGI1NW5t for ; Fri, 14 Jul 2017 13:19:16 +0200 (CEST) X-Originating-IP: 10.58.1.149 Received: from webmail.gandi.net (webmail9-d.mgt.gandi.net [10.58.1.149]) (Authenticated sender: paul@nosphere.org) by relay5-d.mail.gandi.net (Postfix) with ESMTPA id 7F50741C089 for ; Fri, 14 Jul 2017 13:19:16 +0200 (CEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Fri, 14 Jul 2017 13:19:16 +0200 From: Paul Merlin To: dev@polygene.apache.org Subject: Re: Thoughts on Release 3.0 In-Reply-To: References: <59679C21.5070109@apache.org> Message-ID: <5652406848d9cc68537d203438b80999@nosphere.org> X-Sender: paulmerlin@apache.org User-Agent: Roundcube Webmail/1.1.2 archived-at: Fri, 14 Jul 2017 11:19:30 -0000 Le 2017-07-14 02:19, Niclas Hedhman a écrit : >> 3.1 >> - a suite of Gradle plugins: polygene-library, polygene-extension, >> polygene-application .. to make it damn easy to setup the build of >> Polygene apps > > Ok, that would simply fold into the generator? Or is it something to be > published separately? The Gradle plugins would be published on their own and usable directly. The generator would then be able to consume these plugins to simplify the generated builds. >> 3.2 >> - Polygene runs on Jigsaw > > Is Oracle still going ahead with Jigsaw? I thought the EC shot it down? The EC voted against Jigsaw at some point. Recent changes like "--permit-illegal-access" being the default in 9 made the subsequent vote pass. See https://www.jcp.org/en/jsr/results?id=6016 >> - Performance testing, some guarantee that we don't introduce >> regressions would be awesome > > I will offer my new company's resources for this, and it should be > available around 3.2 time frame. Excellent! Basically we'll need to regularly run performance measurements on a well known non-changing, non-busy machine, for the latest release and the head of develop, record the results, assert we don't regress, handle flakiness etc... Then we'll need some nice graph to look at, something like: https://builds.gradle.org/repository/download/Gradle_Check_PerformanceHistoricalCoordinator/3675790:id/results/performance/build/performance-tests/report/tests/clean-assemble-on-largeJavaMultiProject-with-local-cache-(parallel:-true).html ("Login as Guest") >> - Collaboration on the new indexing system / query api is appealing! > > I doubt that I can manage a new indexing/querying on my own, and > looking > forward to heavy collaboration on that. \o/