From dev-return-4633-archive-asf-public=cust-asf.ponee.io@royale.apache.org Thu May 17 10:58:43 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 9839E180634 for ; Thu, 17 May 2018 10:58:42 +0200 (CEST) Received: (qmail 26753 invoked by uid 500); 17 May 2018 08:58:41 -0000 Mailing-List: contact dev-help@royale.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@royale.apache.org Delivered-To: mailing list dev@royale.apache.org Received: (qmail 26736 invoked by uid 99); 17 May 2018 08:58:40 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 May 2018 08:58:40 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id EEEE11A11A5 for ; Thu, 17 May 2018 08:58:39 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.121 X-Spam-Level: X-Spam-Status: No, score=-0.121 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id SjS3SZmbn4mU for ; Thu, 17 May 2018 08:58:38 +0000 (UTC) Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 513CD5F188 for ; Thu, 17 May 2018 08:58:38 +0000 (UTC) Received: by mail-wm0-f45.google.com with SMTP id l1-v6so7567955wmb.2 for ; Thu, 17 May 2018 01:58:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=N6+vqANcBEsmBPjaPTYd1AnrMteyT8za1NyejVX93ec=; b=KiZRItK6s/wysHqDFOu7kwto7tMgQdtYY44c4nYMGIT/LV8JqHF/4MBTWRcjSh9+Pz yc3eRRv1npSbyUD56BCbROCZJIr8udvsKytW6O0zWSxuvai9uP0EspInCgSSjRK8YojV MouyvBQR4tDT5R805iw6CpZL/VTMq2RH6gW3pArjBwukFJai5Nf5GkS82p38clcUjbGe dLZ+Q3vmcj8DIz8GdERuPiNfe0Ur6HhhZrza1pIxDadYziQ3RIMDXpNlkfgRU8bqv4LY qKjuoel7rP6ChVGpqEi1g7SL9Da6F8byYTSEWYZ/4iSIZc4BbXQSgy3DXBYx+VmugbCA XkuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=N6+vqANcBEsmBPjaPTYd1AnrMteyT8za1NyejVX93ec=; b=YC5vQfT05m8KQpVDchLoMDlBQpiZJB1ZkzZ5HdgViOUByLlaHsuS0yftDuzQrdk58L U/d6y7nUIMh6ES0prMheSgtl5qOHSpTMhUz2PeCcWuEv/0cWgVo4cdz0CZ2CiQ5hiOON OLYApZS0V0sMqlCrS1H2cHfdel/Kn4Tb3oZEV/JYIDokBPbjWT/mKvNR1faNNpf9NwZH DJIpxu4liDacqiZPTeuXk3ZdjiGX7inmoX4MmPuRBKS02DR1+Z/HQSIY4xZQOWdi72Zh f2DNcz8BIDvTNsGLCH/QLAA8mpwo4UWA3yffp4zeEn0GCxFeA0yQtOR25eeskXQwVKva iWwA== X-Gm-Message-State: ALKqPweV9vxkFgKNKDJb443/dJ/w82uI/70EX5Xj1WGtkjEAW5i1ZDGo qTSeW2MZHBBUCS50eD7VpdAtxTm9 X-Google-Smtp-Source: AB8JxZrwWv0UDOaMR61n/8FbcBDCh21yAbUPLMJyqEZXEylcF7tgaD8Hkzc/NqDNPH7Zt+l9NThRAw== X-Received: by 2002:a1c:8645:: with SMTP id i66-v6mr1191413wmd.40.1526547517871; Thu, 17 May 2018 01:58:37 -0700 (PDT) Received: from [10.0.0.4] ([185.120.125.17]) by smtp.gmail.com with ESMTPSA id e80-v6sm4218990wmd.1.2018.05.17.01.58.36 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 May 2018 01:58:37 -0700 (PDT) From: Harbs Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: 0.9.3 Release Date: Thu, 17 May 2018 11:58:35 +0300 References: <7900D5AC-630E-4154-ADA7-F3BD2396C4B9@gmail.com> <309EC712-BC3F-47FD-BB02-DBF9EE040ACC@adobe.com> <18A7DEE6-5463-445A-A856-88DFD0AA196E@gmail.com> <06BC00A5-1032-439A-8298-39EC5B0AEE46@gmail.com> <836F372F-872C-4270-AF78-09DE2F3ACF64@gmail.com> To: dev@royale.apache.org In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3273) Sure. Same here. But things are much more stable now. As we move closer to =E2=80=9C1.0=E2=80= =9D, I think we should be more careful about breaking changes and = documenting them when we decide they are necessary. As far as these specific changes go: We haven=E2=80=99t even come to a = conclusion on what (if any) package names should change yet, and = including those changes in a release is premature. If we do change = package names, I=E2=80=99m of the opinion that they should be decided on = and all happen at once to minimize impact on end-users. Does that help clarify things? Thanks, Harbs > On May 17, 2018, at 11:49 AM, Justin Mclean = wrote: >=20 > Hi, >=20 >> We are at the point where people are using Royale in production. = While we can make breaking changes if they are warranted, they should be = kept to an absolute minimum and be carefully considered and well = documented if we do. >=20 > There has been many previous breaking changes that broke the = application I was working on and some more major than this and cost me a = lot of time to fix. Until you make it version 1.0 I think people will = expect that some things may break with a new version. So why should this = be an exception to what has happened before? Saying that however, what = would be good to see is to provide guidance to what users need to change = so their app works with any changes / backward compatibility issues. >=20 > Thanks, > Justin