From dev-return-436-apmail-freemarker-dev-archive=freemarker.apache.org@freemarker.incubator.apache.org Thu Jan 28 23:56:12 2016 Return-Path: X-Original-To: apmail-freemarker-dev-archive@minotaur.apache.org Delivered-To: apmail-freemarker-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EFBBC18D9E for ; Thu, 28 Jan 2016 23:56:12 +0000 (UTC) Received: (qmail 48380 invoked by uid 500); 28 Jan 2016 23:56:12 -0000 Delivered-To: apmail-freemarker-dev-archive@freemarker.apache.org Received: (qmail 48338 invoked by uid 500); 28 Jan 2016 23:56:12 -0000 Mailing-List: contact dev-help@freemarker.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@freemarker.incubator.apache.org Delivered-To: mailing list dev@freemarker.incubator.apache.org Received: (qmail 48322 invoked by uid 99); 28 Jan 2016 23:56:12 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jan 2016 23:56:12 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 37989C32A4 for ; Thu, 28 Jan 2016 23:56:12 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.88 X-Spam-Level: **** X-Spam-Status: No, score=4.88 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, KAM_THEBAT=1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001, XPRIO=1.999] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id FlcN-Kff8Tla for ; Thu, 28 Jan 2016 23:56:04 +0000 (UTC) Received: from fep31.mx.upcmail.net (fep31.mx.upcmail.net [62.179.121.49]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTP id 2660630413 for ; Thu, 28 Jan 2016 23:56:04 +0000 (UTC) Received: from edge04.upcmail.net ([192.168.13.239]) by viefep31-int.chello.at (InterMail vM.8.01.05.18 201-2260-151-151-20140610) with ESMTP id <20160128235556.CFAH7825.viefep31-int.chello.at@edge04.upcmail.net> for ; Fri, 29 Jan 2016 00:55:56 +0100 Received: from [192.168.0.3] ([89.132.92.167]) by edge04.upcmail.net with edge id Bbvw1s00N3cfLdl01bvw1p; Fri, 29 Jan 2016 00:55:56 +0100 X-SourceIP: 89.132.92.167 Date: Fri, 29 Jan 2016 00:55:54 +0100 From: Daniel Dekany X-Mailer: The Bat! (v4.2.36.4) Professional Reply-To: Daniel Dekany X-Priority: 3 (Normal) Message-ID: <1993612130.20160129005554@freemail.hu> To: dev@freemarker.incubator.apache.org Subject: What's next... MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 8bit I mean, unless someone says otherwise... 2.3.24-rc01-incubating is already downloadable at http://www.apache.org/dist/incubator/freemarker/, but as policy says to wait 24 hours before announcement, we do. As it's not a stable release, I don't plan to make it available on Maven Central, only in https://repository.apache.org/service/local/staging/deploy/maven2, though I can be convinced otherwise. After the announcement, I also want to release 2.3.24-rc01-incubating on sourceforge.net. Is that practice OK with the ASF? Around the end of February the final release will be voted on, so please try to make 2.3.24-rc01 fail. Especially the new features. I will be very busy at workplace until the end of March, so any help is highly welcome. For 2.3.24, http://freemarker-online.kenshoo.com/ will need an outputFormat dropdown. (A locale and incompatibleImprovements dropdown would be useful too.) Anyone? After 2.3.24, I think it's time to focus heavily on 3.0, because otherwise FM has just no chance to be sexy/interesting enough to pick up enough contributor activity to survive. As I said earlier, I don't want 3.0 to be a complete rewrite, instead I plant to gradually transform the code, keeping the battle tested parts and the familiar 2.x idioms where reasonable. But surely quite a few parts will have to be trashed and rewritten, and especially at the beginning the commit diffs will be overwhelming. This will be a lot of work BTW. If no one will help at least with tooling, testing, it might happens too slowly. And of course it doesn't mean that 2.3.25 shouldn't go on. It certainly won't be a feature heavy release though. -- Thanks, Daniel Dekany