> So we can assume the current master (commit > a289ecd26257ac4ffaf1bbb686cf06b3a9ececdc) is buildable, right?
Yes, a289ecd26257ac4ffaf1bbb686cf06b3a9ececdc is buildable. > https://github.com/apache/commons-crypto/blob/master/BUILDING.txt > describes build requirements - in particular you need to have openssl library > headers. Good suggestion, I will add the requirements to BUILDING.txt Regards Dapeng -----Original Message----- From: Stian Soiland-Reyes [mailto:st...@apache.org] Sent: Monday, June 06, 2016 11:53 PM To: Commons Developers List Subject: Re: [CRYPTO]1.0.0 Release Plan Makes sense for the first release.. like a pre-release candidate candidate, tested from git. So we can assume the current master (commit a289ecd26257ac4ffaf1bbb686cf06b3a9ececdc) is buildable, right? https://github.com/apache/commons-crypto/blob/master/BUILDING.txt describes build requirements - in particular you need to have openssl library headers. On 6 June 2016 at 15:53, Gary Gregory <garydgreg...@gmail.com> wrote: > 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" <brit...@apache.org> wrote: > >> Hello Dapeng >> >> Sun, Dapeng <dapeng....@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/%3CC >> AB917RJkcNYL4KeRJTo%3D5F7P3A4iyME0TA40GNmuU4RLs5N4KQ%40mail.gmail.com >> %3E >> > [2] >> > >> http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&p >> id=12310464&sorter/field=issuekey&sorter/order=DESC&status=5&status=6 >> > [3] >> > >> http://mail-archives.apache.org/mod_mbox/commons-dev/201606.mbox/%3CC >> ACZkXPyrYvY8NMyQLnT6qMDpNxWiDUudoEw%2BDe%2BYBDHoBBhCzQ%40mail.gmail.c >> om%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 >> > >> > >> -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons http://orcid.org/0000-0001-9842-9718 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
