Return-Path: X-Original-To: apmail-ace-dev-archive@www.apache.org Delivered-To: apmail-ace-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7C9FF10F0C for ; Wed, 13 Nov 2013 09:18:05 +0000 (UTC) Received: (qmail 35162 invoked by uid 500); 13 Nov 2013 09:18:04 -0000 Delivered-To: apmail-ace-dev-archive@ace.apache.org Received: (qmail 35073 invoked by uid 500); 13 Nov 2013 09:18:01 -0000 Mailing-List: contact dev-help@ace.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ace.apache.org Delivered-To: mailing list dev@ace.apache.org Received: (qmail 35047 invoked by uid 99); 13 Nov 2013 09:18:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Nov 2013 09:18:00 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [194.109.24.34] (HELO smtp-vbr14.xs4all.nl) (194.109.24.34) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Nov 2013 09:17:52 +0000 Received: from [10.0.0.33] (planetmarrs.xs4all.nl [82.95.193.148]) (authenticated bits=0) by smtp-vbr14.xs4all.nl (8.13.8/8.13.8) with ESMTP id rAD9HVRs073627 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 13 Nov 2013 10:17:32 +0100 (CET) (envelope-from marcel.offermans@luminis.nl) From: Marcel Offermans Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: Towards a new release and baselining support... Message-Id: Date: Wed, 13 Nov 2013 10:17:30 +0100 To: "" Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\)) X-Mailer: Apple Mail (2.1816) X-Virus-Scanned: by XS4ALL Virus Scanner X-Virus-Checked: Checked by ClamAV on apache.org Hey guys, As you all know, a lot of things have happened recently within the ACE = project. We=92ve rewritten the complete management agent, added quite a = few features to the server and squashed bugs. With all of this work done = I feel we should start working towards a new release now, but I=92d like = to get everbody=92s opinion and check if there are things we forgot = about that really need to make it into a new release. One thing I would like to do is to upgrade to the latest Bndtools 2.2.2 = version and enable support for baselining. Baselining will give us a lot = of tool support to ensure our code (bundles and exported packages) is = semantically versioned. To leverage baselining support there are a = couple of things we need to do: * We need the to start putting @ProviderType and @ConsumerType = annotations on all our APIs. In fact, we need to =93retrofit=94 this to = our 1.0.0 release to ensure the baselining works correctly. These = annotations are not magically available, but we can add them to the = global build path (cnf/ext/defaults.bnd). * We need to keep a copy of all released bundles (the latest version of = each) in a repository to baseline against. Because we don=92t want our = build to break when we=92re off-line I propose we put them in a local = repository. We probably need to build those artifacts with the Eclipse = compiler to prevent problems that will otherwise occur because of = differences between ecj and javac so: checkout with Eclipse, build, = collect all bundles from "generated" folders and publish them into the = releaserepo in cnf. We also want to add them to the -deps artifact so = people can easily get started with a release with baselining enabled. If anybody else has input, speak up! :) WDYT? Greetings, Marcel