From notifications-return-1051-archive-asf-public=cust-asf.ponee.io@thrift.apache.org Thu Feb 18 21:36:14 2021 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mxout1-he-de.apache.org (mxout1-he-de.apache.org [95.216.194.37]) by mx-eu-01.ponee.io (Postfix) with ESMTPS id 77C2518062C for ; Thu, 18 Feb 2021 22:36:14 +0100 (CET) Received: from mail.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mxout1-he-de.apache.org (ASF Mail Server at mxout1-he-de.apache.org) with SMTP id E36BD639A6 for ; Thu, 18 Feb 2021 21:36:13 +0000 (UTC) Received: (qmail 86748 invoked by uid 500); 18 Feb 2021 21:36:13 -0000 Mailing-List: contact notifications-help@thrift.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@thrift.apache.org Delivered-To: mailing list notifications@thrift.apache.org Received: (qmail 86738 invoked by uid 99); 18 Feb 2021 21:36:13 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Feb 2021 21:36:13 +0000 From: =?utf-8?q?GitBox?= To: notifications@thrift.apache.org Subject: =?utf-8?q?=5BGitHub=5D_=5Bthrift=5D_Jens-G_edited_a_comment_on_pull_request_?= =?utf-8?q?=232333=3A_Cherry_picks_for_0=2E14=2E0_branch?= Message-ID: <161368417320.15632.5814817122847747067.asfpy@gitbox.apache.org> Date: Thu, 18 Feb 2021 21:36:13 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit References: In-Reply-To: Jens-G edited a comment on pull request #2333: URL: https://github.com/apache/thrift/pull/2333#issuecomment-781650250 > These are all "corner cases" that only affect a small subset of use cases, Or bad testcase design. I tend refuse to accept such explanations, because it opens the slope to banana software. Sure, shit happens but as developers we should strive to not let it happen. We expect our stuff to work perfectly and are astonished when it does not. The key problem with tests is, that developers are used to think *constructive*. But to write good test cases you have to be *destructive*. Pick the evil guy's hat and ask yourself: What would potentially break it? Then put that it into a test case. > push the built artifacts to package managers Problem is, we can't. [The ASF has very clear rules](http://www.apache.org/legal/release-policy.html): Everything that gets published has to be voted and accepted as a release. We can have internal pre-releases, but are not allowed to upload it to package managers. So if I don't overlook a thing (which is certainly possible) the only way would indeed be to have two official releases. > Publication > > Projects SHALL publish official releases and SHALL NOT publish unreleased materials outside the development community. > > During the process of developing software and preparing a release, various packages are made available to the development community for testing purposes. Projects MUST direct outsiders towards official releases rather than raw source repositories, nightly builds, snapshots, release candidates, or any other similar packages. The only people who are supposed to know about such developer resources are individuals actively participating in development or following the dev list and thus aware of the conditions placed on unreleased materials. ---------------------------------------------------------------- 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: users@infra.apache.org