Return-Path: X-Original-To: apmail-apex-dev-archive@minotaur.apache.org Delivered-To: apmail-apex-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 A6954186E0 for ; Fri, 8 Jan 2016 20:57:11 +0000 (UTC) Received: (qmail 49157 invoked by uid 500); 8 Jan 2016 20:57:11 -0000 Delivered-To: apmail-apex-dev-archive@apex.apache.org Received: (qmail 49095 invoked by uid 500); 8 Jan 2016 20:57:11 -0000 Mailing-List: contact dev-help@apex.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@apex.incubator.apache.org Delivered-To: mailing list dev@apex.incubator.apache.org Received: (qmail 49080 invoked by uid 99); 8 Jan 2016 20:57:11 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jan 2016 20:57:11 +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 D69AC1A039D for ; Fri, 8 Jan 2016 20:57:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.427 X-Spam-Level: X-Spam-Status: No, score=0.427 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.554, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id bYkNIK3O25AT for ; Fri, 8 Jan 2016 20:57:06 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with SMTP id 3C20D25897 for ; Fri, 8 Jan 2016 20:57:05 +0000 (UTC) Received: (qmail 49070 invoked by uid 99); 8 Jan 2016 20:57:04 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jan 2016 20:57:04 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 5813EE01F5; Fri, 8 Jan 2016 20:57:04 +0000 (UTC) From: PramodSSImmaneni To: dev@apex.incubator.apache.org Reply-To: dev@apex.incubator.apache.org References: In-Reply-To: Subject: [GitHub] incubator-apex-core pull request: Checkpoint notification to notif... Content-Type: text/plain Message-Id: <20160108205704.5813EE01F5@git1-us-west.apache.org> Date: Fri, 8 Jan 2016 20:57:04 +0000 (UTC) Github user PramodSSImmaneni commented on the pull request: https://github.com/apache/incubator-apex-core/pull/187#issuecomment-170121776 I rebased it but I am having some second thoughts about a different interface based on the japicmp discussion that @chandnisingh sent earlier. What do you guys think about relaxing the backwards compatibility restriction in the following way in cases where an "optional" callback needs to be added. We ensure that an app compiled against an older version still *runs* by doing runtime checks or with error handling even though the app will *not compile* against the new version without changes. When we are going to a new major version then we can remove those runtime checks. This may be a scenario we might see a few times in future and using a different interface each time might just make this a little problematic. I was planning to look at this over the weekend and in course see if I would need to implement a small utility for the runtime checks that can be reused in the future. Let me know if you think we should be having an email discussion on apex-dev about this rather than this JIRA. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---