Mailing-List: contact empire-db-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: empire-db-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-class: urn:content-classes:message
Subject: Call for planning of new release
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C9A720.D282EACA"
Date: Tue, 17 Mar 2009 17:52:56 +0100
Message-ID: <B297D4737108A0459B66C3A85BB7F9010D68@kn.esteam.de>
Thread-Topic: Call for planning of new release
Thread-Index: AcmnINJLYEKMfdqARmaNwjOC9v443Q==
From: =?iso-8859-1?Q?Rainer_D=F6bele?= <doebele@esteam.de>
To: <empire-db-dev@incubator.apache.org>

------_=_NextPart_001_01C9A720.D282EACA
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi folks,

=20

after our lengthy discussion recently we should now get back to business =
and concentrate on the "release". IMO we have now got enough =
improvements to justify a release.

=20

First we should agree on what the release going to look like?

=20

Surely we need to provide distribution files for download - one for the =
core the other for he Struts2 extensions. What exactly do we provide in =
the files and should we still run on different version numbers for core =
and Struts2?

=20

After we have assembled the distribution files, we have to provide the =
files for voting.

If the vote succeeds we want to register and upload the distribution in =
the central maven repo.

=20

Anything else to consider and who is volunteering to do what?

=20

Regards

Rainer

=20


------_=_NextPart_001_01C9A720.D282EACA--