[ANNOUNCE] Apache Commons Weaver 2.0 released

[Matt Benson]

The Apache Commons Team is pleased to announce the availability of:

Apache Commons Weaver 2.0

Apache Commons Weaver provides an easy way to enhance compiled Java
classes by generating ("weaving") bytecode into those classes.

The release notes can be reviewed at:
http://www.apache.org/dist/commons/weaver/RELEASE-NOTES.txt

Distribution packages can be downloaded from:
https://commons.apache.org/proper/commons-weaver/download_weaver.cgi

When downloading, please verify signatures using the KEYS file available at:
http://www.apache.org/dist/commons

Maven artifacts are also available in the central Maven repository:

http://repo1.maven.org/maven2/org/apache/commons/

The Apache Commons Team

[RESULT] Release Apache Commons Weaver 2.0 based on RC1

[Matt Benson]

Hello, closing this vote as 72 hours have passed. The following votes were
received:

Roberto Cortez: +1
Romain Manni-Bucau: +1
Matt Benson: +1 (binding)
Bruno P. Kinoshita: +1 (binding)
Benedikt Ritter: +1 (binding)
Mark Struberg: +1

With three binding +1s, the release vote passes. Thanks to those who were
able to review the release and cast your vote!

Matt

On Thu, Sep 6, 2018, 5:44 AM Mark Struberg 
wrote:

> checked the source zip from
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/source/
>
> sha512 fine
> sig fine
> builds fine
> RAT passes.
>
> +1
>
>
> LieGrue,
> strub
>
> > Am 04.09.2018 um 17:58 schrieb Matt Benson :
> >
> > I would like to release the [weaver] component.
> >
> > Apache Commons Weaver 2.0 RC1 is available for review at:
> >  *https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/
> > *
> (r29084).
> >
> > Maven artifacts are at:
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1377 .
> >
> > Tested with Oracle JDKs 8 and 10.
> >
> > The Git tag is:
> >
> >
> https://gitbox.apache.org/repos/asf?p=commons-weaver.git;a=tag;h=0eed2d07008fd2bfad32b6f8a03da0299cc61d65
> > .
> >
> > Site (note some links may be broken; this will be fixed when the site
> > is deployed):
> >
> >
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/index.html
> >
> > RAT Report:
> >
> >
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/rat-report.html
> >
> > Quality Reports (PMD/Checkstyle/Findbugs/japicmp):
> >
> >
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-processor/project-reports.html
> >
> >
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer-api/project-reports.html
> >
> >
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer/project-reports.html
> >
> >
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-normalizer/project-reports.html
> >
> >
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-maven-plugin/project-reports.html
> >
> >
> https://dist.apache.org/repos/dist/dev/commons/weaver/2.0-RC1/site/commons-weaver-parent/commons-weaver-antlib/project-reports.html
> >
> > Keys: https://dist.apache.org/repos/dist/release/commons/KEYS
> >
> > Please review the release candidate and vote.
> >  This vote will close no sooner than 72 hours from now, i.e. after
> > 1600UTC 7-September 2018
> >
> >  [ ] +1 Release these artifacts
> >  [ ] +0 OK, but...
> >  [ ] -0 OK, but really should fix...
> >  [ ] -1 I oppose this release because...
> >
> >  Thanks!
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

[Thomas Vandahl]

On 9/7/18 2:11 PM, sebb wrote:
> If the tag contains files that are not in the distribution, why are
> they present at all?

Because they are experimental code, for example. Not ready for prime time.

> If they are needed, why are they not in the distribution?

They are not needed, at least not now.

> Lots of discrepancies means lots of checking.

Yes, I understand that. The clean way to handle this would probably be
to create a release branch, tidy that up and release from there.

Bye, Thomas

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[RESULT][VOTE] Release Apache Commons JCS 2.2.1 based on RC4

[Thomas Vandahl]

On 8/23/18 5:32 PM, Thomas Vandahl wrote:
> I would like to make another attempt to release Apache Commons JCS 2.2.1
> (a bugfix release)
> 
> Apache Commons JCS 2.2.1 RC4 is available for review here:
> 
> https://dist.apache.org/repos/dist/dev/commons/jcs/ (svn revision 28918)

Time to wrap up. The following votes were cast (in order of appearance):

Thomas Vandahl: +1
Romain Manni-Bucau: +1 (non binding)
Benedikt Ritter: +1
Bruno P. Kinoshita: +1

The vote has passed. Thanks to all the voters!

I'll proceed with the release procedure.

Bye, Thomas.

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [VOTE] Release Apache Commons JCS 2.2.1 based on RC4

[sebb]

On 6 September 2018 at 17:24, Thomas Vandahl  wrote:
> On 27.08.18 18:12, Benedikt Ritter wrote:
>> ~/w/a/r/r/t/jcs git:(upstream ⚡ master) > diff -r commons-jcs-2.2.1-RC4/
>> commons-jcs-2.2.1-src
>> Only in commons-jcs-2.2.1-RC4/: .gitignore
>> Only in commons-jcs-2.2.1-RC4/: .svn
>> Only in commons-jcs-2.2.1-RC4/: .travis.yml
>> Only in commons-jcs-2.2.1-src: LICENSE
>> Only in commons-jcs-2.2.1-RC4/: LICENSE.txt
>> Only in commons-jcs-2.2.1-src: NOTICE
>> Only in commons-jcs-2.2.1-RC4/: NOTICE.txt
>> Only in commons-jcs-2.2.1-RC4/: auxiliary-builds
>> Only in commons-jcs-2.2.1-RC4/: checkstyle.xml
>> Only in commons-jcs-2.2.1-RC4/: commons-jcs-sandbox
>> Only in commons-jcs-2.2.1-RC4/: init-git-svn.sh
>> Only in commons-jcs-2.2.1-RC4/: jcache-fast.sh
>> Only in commons-jcs-2.2.1-RC4/: maven-eclipse-codestyle.xml
>>
>> This should be fixed for the next release.
>
> Is it absolutely necessary that the tag contains the exact same files as
> the distribution or would it be sufficient that the tag is able to
> *build* the identical distribution? That has always been my interpretation.

Reviewers need to be able to account for any discrepancies between the
contents to ensure that:
- the dist does not contain spurious files
- the dist is not lacking any required files.

The source distribution also has to be able to build itself.

If the tag contains files that are not in the distribution, why are
they present at all?
If they are needed, why are they not in the distribution?

Lots of discrepancies means lots of checking.

> Bye, Thomas
>
> -
> 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

JDK 12 & JMC 7.0.0 Early Access builds are available

[Rory O'Donnell]

Hi Benedikt,

*JDK 11 build 28 is our first JDK 11 Release Candidate [1]
*

 * JDK 11 build 28 is available at : - jdk.java.net/11/

*JDK 12 Early Access build 10 is available at : - jdk.java.net/12/*

 * Release Notes for JDK 12 [2]
 * *JEPs integrated to JDK 12:*
 o 325: Switch Expressions (Preview [3])
 * *JEPs proposed to target JDK 12:*
 o 326: Raw String Literals (Preview [3])

*FOSS bug fixes in recent builds.*

 * Apache Ant -
   JDK-8209965(b09)

*Other important fixes in JDK 12*

 * Disabled all DES TLS Cipher Suites (JDK-8208350
   )
 o DES-based TLS cipher suites are considered obsolete and should
   no longer be used

*JMC 7.0.0 Early Access build 04 is available at :- 
**http://jdk.java.net/jmc/*


 * Overview - summary [4]
 * These early-access, open-source builds are provided under the
   Universal Permissive License,
   version 1.0.
 * Feedback via the http://bugreport.java.com/
 o Be sure to include jmc application Build id from "Help" - "About
   JDK Mission Control".


Rgds, Rory

[1] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-August/001844.html
[2] http://jdk.java.net/12/release-notes
[3] http://openjdk.java.net/jeps/12
[4] 
https://download.java.net/java/early_access/jmc7/core/common/docs/api/overview-summary.html 



--
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland