Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 21F14200C84 for ; Mon, 29 May 2017 11:35:45 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 208B9160BCE; Mon, 29 May 2017 09:35:45 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 401B6160BC2 for ; Mon, 29 May 2017 11:35:44 +0200 (CEST) Received: (qmail 86038 invoked by uid 500); 29 May 2017 09:35:41 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 86027 invoked by uid 99); 29 May 2017 09:35:41 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 May 2017 09:35:41 +0000 Received: from mail-it0-f42.google.com (mail-it0-f42.google.com [209.85.214.42]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 3484B1A02C0 for ; Mon, 29 May 2017 09:35:41 +0000 (UTC) Received: by mail-it0-f42.google.com with SMTP id g126so24195412ith.0 for ; Mon, 29 May 2017 02:35:41 -0700 (PDT) X-Gm-Message-State: AODbwcAYciDgc1uijgq0zx1ffyQi2JGc/dGTUPd2f0JwfqtciVj37rI2 rKxvaB/JMf8NJAzYCuXQpxY3e+1qLA== X-Received: by 10.36.31.70 with SMTP id d67mr30614813itd.80.1496050539958; Mon, 29 May 2017 02:35:39 -0700 (PDT) MIME-Version: 1.0 Reply-To: elecharny@apache.org Received: by 10.79.144.68 with HTTP; Mon, 29 May 2017 02:35:38 -0700 (PDT) In-Reply-To: References: <4c0c88bc-274f-bc0b-2b53-f8108f1ca2bf@stefan-seelmann.de> From: Emmanuel Lecharny Date: Mon, 29 May 2017 11:35:38 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Release API, Server, Studio To: Apache Directory Developers List Content-Type: multipart/alternative; boundary="001a1144a060003c3d0550a6693c" archived-at: Mon, 29 May 2017 09:35:45 -0000 --001a1144a060003c3d0550a6693c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I have successfully bumped up the dependencies version, for API and ApacheDS. I will start the release tonite. On Mon, May 29, 2017 at 4:39 AM, Emmanuel Lecharny wrote: > > > On Mon, May 29, 2017 at 3:51 AM, Emmanuel L=C3=A9charny > wrote: > >> >> >> Le 28/05/2017 =C3=A0 22:36, Stefan Seelmann a =C3=A9crit : >> > On 05/28/2017 10:21 PM, Emmanuel L=C3=A9charny wrote: >> >> >> >> Le 28/05/2017 =C3=A0 21:15, Stefan Seelmann a =C3=A9crit : >> >>> Hi all, >> >>> >> >>> in order to release a new Studio version we also need to release the >> API >> >>> and the server first because Studio trunk currently depends on >> snapshots >> >>> of both. >> >>> >> >>> Are there any blockers of releasing API and server? >> >> I'll do a quick JIRA check tonite, and give you a status. I'm not sur= e >> >> we have a blocker on the API, we just have to be sure the changes mad= e >> >> in ApacheDS related to the restart/repair are ok for all the OS. I >> guess >> >> we already have some docker instance checking such things. >> > Yes, there is a Jenkins job [1] that tests the installers (zip, tgz, >> > bin, deb). >> > >> > But now I remember there is one thing I wanted to check, if we >> > gracefully shut down ApacheDS, or just kill the process (especially on >> > Windows). >> > >> >>> Should we release another RC of the API, or is it ready for GA? >> >> I *think* we could go with a GA now. >> > Ok, cool. >> >> >> Hmmm, bugs like DIRAPI-227 makes me think that we should wait before >> going with a GA. There is also another fix in MINA that should be made >> whoch will fix DIRAPI-149. >> >> That would be the two important issues to be fixed before we cut a >> 1.0-G1, IMO (I just checked the other issues, and I don't think any of >> them would be problematic for a 1.0) >> > > I double checked, the bug has been fixed in MINA 2.0.15, and we are using > a newer version in trunk, so I closed DIRAPI-227. > > So I think we are ready for a GA, finally :-) > > > I'll upgrade a few dependencies : > org.apache.felix:org.apache.felix.framework ........... 5.6.1 -> 5.6.4 > org.ops4j.pax.exam:pax-exam-container-forked ......... 4.9.2 -> 4.11.0 > org.ops4j.pax.exam:pax-exam-junit4 ................... 4.9.2 -> 4.11.0 > org.ops4j.pax.exam:pax-exam-link-mvn ................. 4.9.2 -> 4.11.0 > ch.qos.logback:logback-classic ........................ 1.1.8 -> 1.2.3 > and cut a release this week. > > Thanks ! > > > -- > Regards, > Cordialement, > Emmanuel L=C3=A9charny > www.iktek.com > --=20 Regards, Cordialement, Emmanuel L=C3=A9charny www.iktek.com --001a1144a060003c3d0550a6693c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I have successfully bumped up the dependencies version, fo= r API and ApacheDS. I will start the release tonite.

On Mon, May 29, 2017 at 4:39 A= M, Emmanuel Lecharny <elecharny@apache.org> wrote:


On Mon, May 29, 2017= at 3:51 AM, Emmanuel L=C3=A9charny <elecharny@gmail.com> = wrote:


Le 28/05/2017 =C3=A0 22:36, Stefan Seelmann a =C3=A9crit :
> On 05/28/2017 10:21 PM, Emmanuel L=C3=A9charny wrote:
>>
>> Le 28/05/2017 =C3=A0 21:15, Stefan Seelmann a =C3=A9crit :
>>> Hi all,
>>>
>>> in order to release a new Studio version we also need to relea= se the API
>>> and the server first because Studio trunk currently depends on= snapshots
>>> of both.
>>>
>>> Are there any blockers of releasing API and server?
>> I'll do a quick JIRA check tonite, and give you a status. I= 9;m not sure
>> we have a blocker on the API, we just have to be sure the changes = made
>> in ApacheDS related to the restart/repair are ok for all the OS. I= guess
>> we already have some docker instance checking such things.
> Yes, there is a Jenkins job [1] that tests the installers (zip, tgz, > bin, deb).
>
> But now I remember there is one thing I wanted to check, if we
> gracefully shut down ApacheDS, or just kill the process (especially on=
> Windows).
>
>>> Should we release another RC of the API, or is it ready for GA= ?
>> I *think* we could go with a GA now.
> Ok, cool.


Hmmm, bugs like DIRAPI-227 makes me think that we should wait before=
going with a GA. There is also another fix in MINA that should be made
whoch will fix DIRAPI-149.

That would be the two important issues to be fixed before we cut a
1.0-G1, IMO (I just checked the other issues, and I don't think any of<= br> them would be problematic for a 1.0)

I double checked, the bug has been fixed in MINA 2.0.15, and= we are using a newer version in trunk, so I closed DIRAPI-227.

So I think we are ready for = a GA, finally :-)


I'll upgrade a few dependencies :
org.apache.felix:org.a= pache.felix.framework ........... 5.6.1 -> 5.6.4
org.ops4j.pax.e= xam:pax-exam-container-forked ......... 4.9.2 -> 4.11.0
org.ops4= j.pax.exam:pax-exam-junit4 ................... 4.9.2 -> 4.11.0
o= rg.ops4j.pax.exam:pax-exam-link-mvn ................. 4.9.2 -> 4.11= .0
ch.qos.logback:logback-classic ........................ 1.1.8 -> 1= .2.3
and cut a release this week.
Thanks !


--
Regards,
Cordialement,
= Emmanuel L=C3=A9charny
www.iktek.com



--
Regards,
Cordialement,
Emm= anuel L=C3=A9charny
w= ww.iktek.com
--001a1144a060003c3d0550a6693c--