Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
MIME-Version: 1.0
In-Reply-To: <CAB917RLxSGOqFSHzM6ko6F+DUciUNj=R0fFoSDzATKXwQTUjZw@mail.gmail.com>
References: <B957EE1AFDEBFD4B934BCF11804A23DC0489032F@shsmsx102.ccr.corp.intel.com>
	<B957EE1AFDEBFD4B934BCF11804A23DC0489037C@shsmsx102.ccr.corp.intel.com>
	<CAB917RLxSGOqFSHzM6ko6F+DUciUNj=R0fFoSDzATKXwQTUjZw@mail.gmail.com>
Date: Mon, 6 Jun 2016 07:53:17 -0700
Message-ID: <CACZkXPyusOmvtTgTRrOy4q3cByYTUvCoFWM5c1MU2t3joUC=6g@mail.gmail.com>
Subject: Re: [CRYPTO]1.0.0 Release Plan
From: Gary Gregory <garydgregory@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: multipart/alternative; boundary=001a1141b84899199705349d3bbe
archived-at: Mon, 06 Jun 2016 14:53:24 -0000

--001a1141b84899199705349d3bbe
Content-Type: text/plain; charset=UTF-8

Why don't you give us a couple of days before rolling an RC, I for one,
would like to review the project a little more carefully. This would avoid
wasting time on failed RCs and give an opportunity for others committers
and PMC members to make any changes they think should be be done. Could be
things like reviewing PMD, CPD, and Checkstyle reports, and so on. Mayve
announce something like, "I plan on rolling an RC and Friday" or something
like that.

Gary
On Jun 6, 2016 2:49 AM, "Benedikt Ritter" <britter@apache.org> wrote:

> Hello Dapeng
>
> Sun, Dapeng <dapeng.sun@intel.com> schrieb am Mo., 6. Juni 2016 um
> 11:13 Uhr:
>
> > Hello,
> >
> > Apache Commons CRYPTO was established at May 9, 2016[1], There are
> > presently numbers of resolved issues fix in CRYPTO[2]. Recently, we also
> > fixed the legal issue[3].
> >
> > With the first release, we can begin to promote CRYPTO to other Apache
> > components, like Apache Hadoop, Apache Spark, so that they can benefit
> the
> > higher performance improvement from Apache Commons Crypto.
> >
> > We plan the following three opening features to next release(I think it
> > should be 1.1.0): GCM support[4], JNACipher implementation[5] and
> benchmark
> > tool[6]. Please let me know if there is anything need to be done before
> the
> > release.
> >
> >
> Sounds good to me. Let me know if you need help preparing the RC.
>
> Benedikt
>
>
> >
> > Regards
> > Dapeng
> >
> >
> > [1]
> >
> http://mail-archives.apache.org/mod_mbox/commons-dev/201605.mbox/%3CCAB917RJkcNYL4KeRJTo%3D5F7P3A4iyME0TA40GNmuU4RLs5N4KQ%40mail.gmail.com%3E
> > [2]
> >
> http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310464&sorter/field=issuekey&sorter/order=DESC&status=5&status=6
> > [3]
> >
> http://mail-archives.apache.org/mod_mbox/commons-dev/201606.mbox/%3CCACZkXPyrYvY8NMyQLnT6qMDpNxWiDUudoEw%2BDe%2BYBDHoBBhCzQ%40mail.gmail.com%3E
> > [4] https://github.com/apache/commons-crypto/pull/44
> > [5] https://github.com/apache/commons-crypto/pull/47
> > [6] https://github.com/apache/commons-crypto/pull/1
> >
> >
>

--001a1141b84899199705349d3bbe--