Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: Release API, Server, Studio
To: dev@directory.apache.org
References: <4c0c88bc-274f-bc0b-2b53-f8108f1ca2bf@stefan-seelmann.de>
 <b2653a77-3e88-628f-48f5-db4b83dd03fa@gmail.com>
 <addf60bf-c264-99ef-433e-e57436d4ce87@stefan-seelmann.de>
From: =?UTF-8?Q?Emmanuel_L=c3=a9charny?= <elecharny@gmail.com>
Message-ID: <a27b0fd9-9f63-783c-e9c6-acfc525258f9@gmail.com>
Date: Mon, 29 May 2017 03:51:04 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0)
 Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <addf60bf-c264-99ef-433e-e57436d4ce87@stefan-seelmann.de>
Content-Type: text/plain; charset=utf-8
Content-Language: fr
Content-Transfer-Encoding: quoted-printable
archived-at: Mon, 29 May 2017 01:51:15 -0000


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 snapsh=
ots
>>> 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 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 gue=
ss
>> 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)

So 1.0.0-RC3 for the moment, as I won't have time to fix MINA and cut a
release before this week-end...

--=20
Emmanuel Lecharny

Symas.com
directory.apache.org