Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <557041BD.4040604@gmail.com>
Date: Thu, 04 Jun 2015 14:17:01 +0200
From: =?UTF-8?B?RW1tYW51ZWwgTMOpY2hhcm55?= <elecharny@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: Kerby release
References: 
 <CAB8XdGAgooD6oMbUdcM+Vqqxtn76D1q3YHSEN=DEhENV-PSdRQ@mail.gmail.com>
	<8D5F7E3237B3ED47B84CF187BB17B66611B36589@SHSMSX103.ccr.corp.intel.com>
	<CAB8XdGDOh0omBr_05pCs05KrSJK53b0q--Q2C9Es28zFoiFNVA@mail.gmail.com>
	<8D5F7E3237B3ED47B84CF187BB17B66611B6A3A2@SHSMSX103.ccr.corp.intel.com>
 <CAB8XdGCLr3COzEXtaESQej+CLrKjtLSVRuviHDwTsR=J_MVqZg@mail.gmail.com>
 <556F2BD4.1020200@gmail.com>
 <8D5F7E3237B3ED47B84CF187BB17B66611B6A914@SHSMSX103.ccr.corp.intel.com>
In-Reply-To: 
 <8D5F7E3237B3ED47B84CF187BB17B66611B6A914@SHSMSX103.ccr.corp.intel.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Le 04/06/15 02:38, Zheng, Kai a =C3=A9crit :
> Thanks Colm and Emmanuel for the thoughts and help!
>
>>> The numering scheme we use for ApacheDS is a bit complex and its hist=
ory is long...
> The very good history and I see why. Maybe we could have a major releas=
e like 2.0.0 claiming no backward support?=20

Considering that we already don't support 1.0, it's clear that 2.0 will
not provide any backward support ;-)
>
>>> Keep in mind that we release sources ! Now, you can also build some c=
onvenient packages, but this will be a side product.
> I see. So as Colm explained, maybe we could have some container modules=
 for such convenient packages?=20

Ok, let me be a bit clearer : we should absolutely focus on sources, but
we *can* provide binaries ! Actually, this is what we do.

The way to do it is to have special Maven prodiles to build all the
packages you want.


>
>>> I can definitively give a hand, as I have been releasing most of the =
other projects for years now...
> This really sounds great to me. I'm much confident now, with your takin=
g and also Colm's help. I will try my best for the release in the followi=
ng.
>
> So for next step, we will need a master JIRA for the release, and a tar=
get version (1.0-RC1 ?).
I can create those versions in JIRA. The problem is that we already have
existing version for Kerberos :
https://issues.apache.org/jira/browse/DIRKRB/?selectedTab=3Dcom.atlassian=
=2Ejira.jira-projects-plugin:versions-panel

Which is a bit strange considering we never ever released any Kerberos
code !

I think it's related to the ApacheDS releases. I will remove those versio=
ns.

I think we need a 1.0.0-RC1, a 1.0.0-GA (for the final version), and a
2.0.0 version for future changes. Is that fine ?


>  I would help sort out all the issues in the question for us to discuss=
 and determine further. For each one desired for the release, we would en=
sure assignment and commitment in some certain time with higher priority,=
 as Colm proposed initially in this thread. Sound good to go?

Atm, what I'd like to have is a release on one of the core Kerby
component : ASN.1. We can use that as an exercise, and I'd like to use
it in ApacheDS, as a separate module.

Wdyt ?