From dev-return-30896-apmail-geode-dev-archive=geode.apache.org@geode.apache.org Wed Apr 3 00:20:41 2019 Return-Path: X-Original-To: apmail-geode-dev-archive@minotaur.apache.org Delivered-To: apmail-geode-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 BADD818AFF for ; Wed, 3 Apr 2019 00:20:41 +0000 (UTC) Received: (qmail 46047 invoked by uid 500); 3 Apr 2019 00:20:41 -0000 Delivered-To: apmail-geode-dev-archive@geode.apache.org Received: (qmail 45974 invoked by uid 500); 3 Apr 2019 00:20:41 -0000 Mailing-List: contact dev-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list dev@geode.apache.org Received: (qmail 45939 invoked by uid 99); 3 Apr 2019 00:20:40 -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; Wed, 03 Apr 2019 00:20:40 +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 50F13183989 for ; Wed, 3 Apr 2019 00:20:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.664 X-Spam-Level: X-Spam-Status: No, score=0.664 tagged_above=-999 required=6.31 tests=[KHOP_DYNAMIC=1.364, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 00gvhGVSLno3 for ; Wed, 3 Apr 2019 00:20:39 +0000 (UTC) Received: from mx0b-00296801.pphosted.com (mx0b-00296801.pphosted.com [148.163.153.148]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id DD9DF624B1 for ; Wed, 3 Apr 2019 00:20:38 +0000 (UTC) Received: from pps.filterd (m0114584.ppops.net [127.0.0.1]) by mx0b-00296801.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x330Fx6N031597 for ; Wed, 3 Apr 2019 00:20:38 GMT Received: from mail-pl1-f200.google.com (mail-pl1-f200.google.com [209.85.214.200]) by mx0b-00296801.pphosted.com with ESMTP id 2rkgjxj9nb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Wed, 03 Apr 2019 00:20:38 +0000 Received: by mail-pl1-f200.google.com with SMTP id f7so3330188plr.10 for ; Tue, 02 Apr 2019 17:20:38 -0700 (PDT) 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:date :subject:message-id:references:in-reply-to:to; bh=QhXJAT250vDdmJFUiNkB5EP9IBDIgoZ/S5Ue9zLrWX0=; b=Gt9GzMjj1OAds+MVzkYMAe6atmZObeBiK/E4LBerbzQfzjCgHiZdXRKJyKAY38kvLb cfuyle3eyjkcUNQ7GatTULR881uKlru1mUNZA8G5MzzaebGwQT++uSdjhbU5vAOsiwcx unbv+XxxTYaLM0njCzMmL0X5c2UGk8xr4Ro9hjSSsl7qtQ6s5SemRlozZaLBV+CIt0W6 CNJP+D3eu3OU1eJCilmkkbgMygRoH9LYx3DrPT9sOMx8aCBaSRFQQrjIawjSGSLMLgmC PEP9ipnZgTD10CWS7riUmD6T/+PTn958aX7xwM8xLiD0ye/BEMmwxmiNvD6nPCOvDzBZ inBg== X-Gm-Message-State: APjAAAVQCKttPLtkhPbwKYSVOSZXHCaXtq0090oClJqhEn/s8X0Q54+3 +573h8hBQKESCE8yuHu4jr2FMLLfplySiZBctq7VplhfwuP6xgV8kr93N/Es+8AOWeNu9HCp4dt qna5cN/tdeE2AHqni4nTfg2vxdRld5IN6WvAUtmk= X-Received: by 2002:a17:902:be0a:: with SMTP id r10mr59275956pls.4.1554250836999; Tue, 02 Apr 2019 17:20:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqx4vLe/tyzL17/4W5P4j7uNQ/fys+vk4f/gZd4q6St55wRcPf1NKdyX3bamiLA2K6p+TR+E1Q== X-Received: by 2002:a17:902:be0a:: with SMTP id r10mr59275932pls.4.1554250836747; Tue, 02 Apr 2019 17:20:36 -0700 (PDT) Received: from ?IPv6:2600:380:7022:290f:c9eb:da5f:d9ea:9432? ([2600:380:7022:290f:c9eb:da5f:d9ea:9432]) by smtp.gmail.com with ESMTPSA id m10sm16018206pgq.42.2019.04.02.17.20.35 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Apr 2019 17:20:35 -0700 (PDT) From: Jacob Barrett Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Tue, 2 Apr 2019 17:20:34 -0700 Subject: Re: [DISCUSS] Move or remove org.apache.geode.admin Message-Id: <0EB59265-E5A1-4070-8DB7-84347D0D0941@pivotal.io> References: In-Reply-To: To: dev@geode.apache.org X-Mailer: iPhone Mail (16E227) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-04-02_11:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=805 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1904030000 > On Apr 2, 2019, at 5:04 PM, Dan Smith wrote: >=20 > I think the best course of action is probably to remove it entirely. > However, this does bring up a couple of questions: >=20 > 1) Is it ok in general to remove deprecated API in a non X.0 release (eg > geode 1.10 instead of geode 2.0)? I think a deprecated API is no longer API after a major version increment. T= he deprecated symbols can be removed anytime after the major release with me= rely a notice in the release notes. I think its unrealistic to expect all de= precated symbols be removed for the x.0 release. > 2) How about in this case, when this feature has been deprecated for so > long, and may or may not work? Given that this API was effectively deprecated in version 0 of Geode and was= never part of the release API in 1 it is fair game now. Time should not be a= factor, just major version number.=20 -Jake