[VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

classic Classic list List threaded Threaded
20 messages Options
Reply | Threaded
Open this post in threaded view
|

[VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Thomas Vandahl
I would like to beta-release the [jcs] component.
The issues found with RC1 have been addressed.

Apache Commons JCS 2.0-beta-2 RC2 is available for review at:
  https://dist.apache.org/repos/dist/dev/commons/jcs/ (r16762).

Maven artifacts are at:
  https://repository.apache.org/content/repositories/orgapachecommons-1218 .

The Subversion tag is:


https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.0-beta-2
(r1767436).

The release notes are at:


https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.0-beta-2/RELEASE-NOTES.txt
(r1767436).

The staged site is available as a tarball at

https://dist.apache.org/repos/dist/dev/commons/jcs/commons-jcs-site-2.0-beta-2.tar.gz
(r16762).

Please review the release candidate and vote.

  [ ] +1 Release these artifacts
  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...

Bye, Thomas



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Romain Manni-Bucau
+1, thanks Thomas


Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://blog-rmannibucau.rhcloud.com> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
<https://javaeefactory-rmannibucau.rhcloud.com>

2016-11-01 9:24 GMT+01:00 Thomas Vandahl <[hidden email]>:

> I would like to beta-release the [jcs] component.
> The issues found with RC1 have been addressed.
>
> Apache Commons JCS 2.0-beta-2 RC2 is available for review at:
>   https://dist.apache.org/repos/dist/dev/commons/jcs/ (r16762).
>
> Maven artifacts are at:
>   https://repository.apache.org/content/repositories/orgapachecommons-1218
> .
>
> The Subversion tag is:
>
>
> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/
> commons-jcs-2.0-beta-2
> (r1767436).
>
> The release notes are at:
>
>
> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/
> commons-jcs-2.0-beta-2/RELEASE-NOTES.txt
> (r1767436).
>
> The staged site is available as a tarball at
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/commons-
> jcs-site-2.0-beta-2.tar.gz
> (r16762).
>
> Please review the release candidate and vote.
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
> Bye, Thomas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Johannes Weberhofer
+1 from my side.


When I build JCS on a NFS share, the following tests fail:

testWrite_128BlockElement(org.apache.commons.jcs.auxiliary.disk.block.BlockDiskUnitTest)  Time elapsed: 0.015 sec  <<< FAILURE!
junit.framework.AssertionFailedError: Wrong number of blocks recorded. expected:<128> but was:<256>
        at org.apache.commons.jcs.auxiliary.disk.block.BlockDiskUnitTest.testWrite_128BlockElement(BlockDiskUnitTest.java:214)

testWrite_DoubleBlockElement(org.apache.commons.jcs.auxiliary.disk.block.BlockDiskUnitTest)  Time elapsed: 0.002 sec  <<< FAILURE!
junit.framework.AssertionFailedError: Wrong number of blocks recorded. expected:<2> but was:<4>
        at org.apache.commons.jcs.auxiliary.disk.block.BlockDiskUnitTest.testWrite_DoubleBlockElement(BlockDiskUnitTest.java:188)



java.sql.SQLException: Table already exists: JCS_STORE_MYSQL in statement [CREATE CACHED TABLE JCS_STORE_MYSQL]
        at org.apache.commons.jcs.auxiliary.disk.jdbc.mysql.MySQLDiskCacheHsqlBackedUnitTest.setupDatabase(MySQLDiskCacheHsqlBackedUnitTest.java:65)

Running org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDataSourceFactoryUnitTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.11 sec - in org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDataSourceFactoryUnitTest
Running org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCacheSharedPoolUnitTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.315 sec <<< FAILURE! - in org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCacheSharedPoolUnitTest
testSimpleJDBCPutGetWithHSQL(org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCacheSharedPoolUnitTest)  Time elapsed: 0.281 sec  <<< ERROR!
java.sql.SQLException: Table already exists: JCS_STORE_0 in statement [CREATE CACHED TABLE JCS_STORE_0]
        at org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCacheSharedPoolUnitTest.testSimpleJDBCPutGetWithHSQL(JDBCDiskCacheSharedPoolUnitTest.java:70)

Running org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCacheUnitTest
Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.396 sec <<< FAILURE! - in org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCacheUnitTest
testInitializePoolAccess_withPoolName(org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCacheUnitTest)  Time elapsed: 0.359 sec  <<< ERROR!
java.sql.SQLException: Table already exists: JCSTESTTABLE_INITIALIZEPOOLACCESS in statement [CREATE CACHED TABLE JCSTESTTABLE_InitializePoolAccess]
        at org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCacheUnitTest.testInitializePoolAccess_withPoolName(JDBCDiskCacheUnitTest.java:203)

testSimpleJDBCPutGetWithHSQL(org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCacheUnitTest)  Time elapsed: 0.001 sec  <<< ERROR!
java.sql.SQLException: Table already exists: JCS_STORE2 in statement [CREATE CACHED TABLE JCS_STORE2]
        at org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCacheUnitTest.testSimpleJDBCPutGetWithHSQL(JDBCDiskCacheUnitTest.java:76)

Running org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCacheShrinkUnitTest
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.353 sec <<< FAILURE! - in org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCacheShrinkUnitTest
org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCacheShrinkUnitTest  Time elapsed: 0.353 sec  <<< ERROR!
java.sql.SQLException: Table already exists: JCS_STORE_SHRINK in statement [CREATE CACHED TABLE JCS_STORE_SHRINK]
        at org.apache.commons.jcs.auxiliary.disk.jdbc.JDBCDiskCacheShrinkUnitTest.setupDatabase(JDBCDiskCacheShrinkUnitTest.java:66)



Thank you!
Johannes


Am 01.11.2016 um 21:33 schrieb Romain Manni-Bucau:

> +1, thanks Thomas
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2016-11-01 9:24 GMT+01:00 Thomas Vandahl <[hidden email]>:
>
>> I would like to beta-release the [jcs] component.
>> The issues found with RC1 have been addressed.
>>
>> Apache Commons JCS 2.0-beta-2 RC2 is available for review at:
>>   https://dist.apache.org/repos/dist/dev/commons/jcs/ (r16762).
>>
>> Maven artifacts are at:
>>   https://repository.apache.org/content/repositories/orgapachecommons-1218
>> .
>>
>> The Subversion tag is:
>>
>>
>> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/
>> commons-jcs-2.0-beta-2
>> (r1767436).
>>
>> The release notes are at:
>>
>>
>> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/
>> commons-jcs-2.0-beta-2/RELEASE-NOTES.txt
>> (r1767436).
>>
>> The staged site is available as a tarball at
>>
>> https://dist.apache.org/repos/dist/dev/commons/jcs/commons-
>> jcs-site-2.0-beta-2.tar.gz
>> (r16762).
>>
>> Please review the release candidate and vote.
>>
>>   [ ] +1 Release these artifacts
>>   [ ] +0 OK, but...
>>   [ ] -0 OK, but really should fix...
>>   [ ] -1 I oppose this release because...
>>
>> Bye, Thomas
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>

--
Johannes Weberhofer
Weberhofer GmbH, Austria, Vienna

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

garydgregory
In reply to this post by Thomas Vandahl
+1

MD5, SHA-1, ASC OK. Everyone is reviewing these as well, right?

Everything builds OK, site and all. Each modules could use a better
description than "Apache Commons JCS is a distributed, versatile caching
system."

Gary

On Tue, Nov 1, 2016 at 1:24 AM, Thomas Vandahl <[hidden email]> wrote:

> I would like to beta-release the [jcs] component.
> The issues found with RC1 have been addressed.
>
> Apache Commons JCS 2.0-beta-2 RC2 is available for review at:
>   https://dist.apache.org/repos/dist/dev/commons/jcs/ (r16762).
>
> Maven artifacts are at:
>   https://repository.apache.org/content/repositories/orgapachecommons-1218
> .
>
> The Subversion tag is:
>
>
> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/
> commons-jcs-2.0-beta-2
> (r1767436).
>
> The release notes are at:
>
>
> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/
> commons-jcs-2.0-beta-2/RELEASE-NOTES.txt
> (r1767436).
>
> The staged site is available as a tarball at
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/commons-
> jcs-site-2.0-beta-2.tar.gz
> (r16762).
>
> Please review the release candidate and vote.
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
> Bye, Thomas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
E-Mail: [hidden email] | [hidden email]
Java Persistence with Hibernate, Second Edition
<https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8>

<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
JUnit in Action, Second Edition
<https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22>

<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
Spring Batch in Action
<https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Thomas Vandahl
In reply to this post by Thomas Vandahl
On 01.11.16 09:24, Thomas Vandahl wrote:
>   [X] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...

My vote.

Bye, Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

garydgregory
Time to tally?

Gary

On Sat, Nov 5, 2016 at 4:38 AM, Thomas Vandahl <[hidden email]> wrote:

> On 01.11.16 09:24, Thomas Vandahl wrote:
> >   [X] +1 Release these artifacts
> >   [ ] +0 OK, but...
> >   [ ] -0 OK, but really should fix...
> >   [ ] -1 I oppose this release because...
>
> My vote.
>
> Bye, Thomas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
E-Mail: [hidden email] | [hidden email]
Java Persistence with Hibernate, Second Edition
<https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8>

<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
JUnit in Action, Second Edition
<https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22>

<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
Spring Batch in Action
<https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Thomas Vandahl
On 05.11.16 20:24, Gary Gregory wrote:
> Time to tally?

I would like to. However, AFAIK, we are one PMC vote short.

Bye, Thomas.



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

garydgregory
Good to know, TY. Hopefully someone will take the time to review over the
weekend.

Gary

On Sat, Nov 5, 2016 at 12:37 PM, Thomas Vandahl <[hidden email]> wrote:

> On 05.11.16 20:24, Gary Gregory wrote:
> > Time to tally?
>
> I would like to. However, AFAIK, we are one PMC vote short.
>
> Bye, Thomas.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
E-Mail: [hidden email] | [hidden email]
Java Persistence with Hibernate, Second Edition
<https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8>

<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
JUnit in Action, Second Edition
<https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22>

<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
Spring Batch in Action
<https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Oliver Heger-3
It seems that there are many breaking changes between this release and
beta1; for instance, the clirr report for the core component lists
numerous errors. Is it not against Commons policy to publish
incompatible artifacts with the same maven and package coordinates to
Maven central?

Oliver

Am 05.11.2016 um 20:50 schrieb Gary Gregory:

> Good to know, TY. Hopefully someone will take the time to review over the
> weekend.
>
> Gary
>
> On Sat, Nov 5, 2016 at 12:37 PM, Thomas Vandahl <[hidden email]> wrote:
>
>> On 05.11.16 20:24, Gary Gregory wrote:
>>> Time to tally?
>>
>> I would like to. However, AFAIK, we are one PMC vote short.
>>
>> Bye, Thomas.
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Thomas Vandahl
Hi Oliver,

On 05.11.16 21:18, Oliver Heger wrote:
> It seems that there are many breaking changes between this release and
> beta1; for instance, the clirr report for the core component lists
> numerous errors. Is it not against Commons policy to publish
> incompatible artifacts with the same maven and package coordinates to
> Maven central?

I thought that is why we call it "beta"? It basically boils down again
to the question what should be considered a public API (which btw hasn't
changed since beta-1).
I have no problem with changing the coordinates but I'm pretty sure that
the next iteration to 2.0 final will introduce more incompatibilities
and we may run out of coordinates...

As I see it, we are still in the transition from 1.3
(org.apache.jcs:jcs) to 2.0 (org.apache.commons.jcs:commons-jcs-core)
but I'm ready to change whatever is necessary to get this out of the door.

Bye, Thomas.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

garydgregory
There is no need to maintain BC since 2.0 is not out. Changing package
names and Maven coordinates must also happen hand in hand. Changing one
means changing the other.

Gary

On Nov 5, 2016 1:37 PM, "Thomas Vandahl" <[hidden email]> wrote:

> Hi Oliver,
>
> On 05.11.16 21:18, Oliver Heger wrote:
> > It seems that there are many breaking changes between this release and
> > beta1; for instance, the clirr report for the core component lists
> > numerous errors. Is it not against Commons policy to publish
> > incompatible artifacts with the same maven and package coordinates to
> > Maven central?
>
> I thought that is why we call it "beta"? It basically boils down again
> to the question what should be considered a public API (which btw hasn't
> changed since beta-1).
> I have no problem with changing the coordinates but I'm pretty sure that
> the next iteration to 2.0 final will introduce more incompatibilities
> and we may run out of coordinates...
>
> As I see it, we are still in the transition from 1.3
> (org.apache.jcs:jcs) to 2.0 (org.apache.commons.jcs:commons-jcs-core)
> but I'm ready to change whatever is necessary to get this out of the door.
>
> Bye, Thomas.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Oliver Heger-3
Hi,

sorry, I don't want to stand in the way of the release. It is just that
in the past we used to be very careful with artifacts deployed to Maven
central and their compatibility. When I did alpha and beta releases for
[configuration] 2.0 it was decided that these artifacts must not be
published to Maven central because incompatibilities between succeeding
alphas/betas or the final 2.0 version are likely.

If the JCS betas are going to Maven central, I therefore assumed that
some means were taken to deal with incompatibilities. Otherwise, if some
3rd party project has the (stupid) idea to depend on such a beta, we are
in jar hell.

Oliver

Am 05.11.2016 um 23:52 schrieb Gary Gregory:

> There is no need to maintain BC since 2.0 is not out. Changing package
> names and Maven coordinates must also happen hand in hand. Changing one
> means changing the other.
>
> Gary
>
> On Nov 5, 2016 1:37 PM, "Thomas Vandahl" <[hidden email]> wrote:
>
>> Hi Oliver,
>>
>> On 05.11.16 21:18, Oliver Heger wrote:
>>> It seems that there are many breaking changes between this release and
>>> beta1; for instance, the clirr report for the core component lists
>>> numerous errors. Is it not against Commons policy to publish
>>> incompatible artifacts with the same maven and package coordinates to
>>> Maven central?
>>
>> I thought that is why we call it "beta"? It basically boils down again
>> to the question what should be considered a public API (which btw hasn't
>> changed since beta-1).
>> I have no problem with changing the coordinates but I'm pretty sure that
>> the next iteration to 2.0 final will introduce more incompatibilities
>> and we may run out of coordinates...
>>
>> As I see it, we are still in the transition from 1.3
>> (org.apache.jcs:jcs) to 2.0 (org.apache.commons.jcs:commons-jcs-core)
>> but I'm ready to change whatever is necessary to get this out of the door.
>>
>> Bye, Thomas.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

garydgregory
On Sun, Nov 6, 2016 at 7:44 AM, Oliver Heger <[hidden email]>
wrote:

> Hi,
>
> sorry, I don't want to stand in the way of the release. It is just that
> in the past we used to be very careful with artifacts deployed to Maven
> central and their compatibility. When I did alpha and beta releases for
> [configuration] 2.0 it was decided that these artifacts must not be
> published to Maven central because incompatibilities between succeeding
> alphas/betas or the final 2.0 version are likely.
>
> If the JCS betas are going to Maven central, I therefore assumed that
> some means were taken to deal with incompatibilities. Otherwise, if some
> 3rd party project has the (stupid) idea to depend on such a beta, we are
> in jar hell.
>

That is a risk indeed. The alternatives would be:

 - Release betas under a beta package name
 - Not release betas at all but just tag the software in svn/git. This
makes is effectively impossible to use from Maven/Ivy/AndSoOn.

Gary

>
> Oliver
>
> Am 05.11.2016 um 23:52 schrieb Gary Gregory:
> > There is no need to maintain BC since 2.0 is not out. Changing package
> > names and Maven coordinates must also happen hand in hand. Changing one
> > means changing the other.
> >
> > Gary
> >
> > On Nov 5, 2016 1:37 PM, "Thomas Vandahl" <[hidden email]> wrote:
> >
> >> Hi Oliver,
> >>
> >> On 05.11.16 21:18, Oliver Heger wrote:
> >>> It seems that there are many breaking changes between this release and
> >>> beta1; for instance, the clirr report for the core component lists
> >>> numerous errors. Is it not against Commons policy to publish
> >>> incompatible artifacts with the same maven and package coordinates to
> >>> Maven central?
> >>
> >> I thought that is why we call it "beta"? It basically boils down again
> >> to the question what should be considered a public API (which btw hasn't
> >> changed since beta-1).
> >> I have no problem with changing the coordinates but I'm pretty sure that
> >> the next iteration to 2.0 final will introduce more incompatibilities
> >> and we may run out of coordinates...
> >>
> >> As I see it, we are still in the transition from 1.3
> >> (org.apache.jcs:jcs) to 2.0 (org.apache.commons.jcs:commons-jcs-core)
> >> but I'm ready to change whatever is necessary to get this out of the
> door.
> >>
> >> Bye, Thomas.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
E-Mail: [hidden email] | [hidden email]
Java Persistence with Hibernate, Second Edition
<https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8>

<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
JUnit in Action, Second Edition
<https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22>

<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
Spring Batch in Action
<https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Romain Manni-Bucau
Le 8 nov. 2016 07:25, "Gary Gregory" <[hidden email]> a écrit :

>
> On Sun, Nov 6, 2016 at 7:44 AM, Oliver Heger <[hidden email]
>
> wrote:
>
> > Hi,
> >
> > sorry, I don't want to stand in the way of the release. It is just that
> > in the past we used to be very careful with artifacts deployed to Maven
> > central and their compatibility. When I did alpha and beta releases for
> > [configuration] 2.0 it was decided that these artifacts must not be
> > published to Maven central because incompatibilities between succeeding
> > alphas/betas or the final 2.0 version are likely.
> >
> > If the JCS betas are going to Maven central, I therefore assumed that
> > some means were taken to deal with incompatibilities. Otherwise, if some
> > 3rd party project has the (stupid) idea to depend on such a beta, we are
> > in jar hell.
> >
>
> That is a risk indeed. The alternatives would be:
>

This is not really valuable options IMO

>  - Release betas under a beta package name

Breaks more than changing almost no API - meaning of beta is "we are almost
there".

>  - Not release betas at all but just tag the software in svn/git. This
> makes is effectively impossible to use from Maven/Ivy/AndSoOn.
>

Basically means it doesnt exist.

FYI we use jcs in tomee as jcache implementation - no api risk - and needed
to fork it to be able to release. This maybe means JCS is now no more a
single API delivery which makes things more complex.

That said, and on another topic, the rule of commons on changing packages
shouldnt apply on alpha and beta otherwise this way of working doesnt make
any sense anymore (= no way to get feedback since people know they will be
fully broken anyway and not just a bit or not fully implemented).

> Gary
>
> >
> > Oliver
> >
> > Am 05.11.2016 um 23:52 schrieb Gary Gregory:
> > > There is no need to maintain BC since 2.0 is not out. Changing package
> > > names and Maven coordinates must also happen hand in hand. Changing
one

> > > means changing the other.
> > >
> > > Gary
> > >
> > > On Nov 5, 2016 1:37 PM, "Thomas Vandahl" <[hidden email]> wrote:
> > >
> > >> Hi Oliver,
> > >>
> > >> On 05.11.16 21:18, Oliver Heger wrote:
> > >>> It seems that there are many breaking changes between this release
and
> > >>> beta1; for instance, the clirr report for the core component lists
> > >>> numerous errors. Is it not against Commons policy to publish
> > >>> incompatible artifacts with the same maven and package coordinates
to
> > >>> Maven central?
> > >>
> > >> I thought that is why we call it "beta"? It basically boils down
again
> > >> to the question what should be considered a public API (which btw
hasn't
> > >> changed since beta-1).
> > >> I have no problem with changing the coordinates but I'm pretty sure
that

> > >> the next iteration to 2.0 final will introduce more incompatibilities
> > >> and we may run out of coordinates...
> > >>
> > >> As I see it, we are still in the transition from 1.3
> > >> (org.apache.jcs:jcs) to 2.0 (org.apache.commons.jcs:commons-jcs-core)
> > >> but I'm ready to change whatever is necessary to get this out of the
> > door.
> > >>
> > >> Bye, Thomas.
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: [hidden email]
> > >> For additional commands, e-mail: [hidden email]
> > >>
> > >>
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
>
> --
> E-Mail: [hidden email] | [hidden email]
> Java Persistence with Hibernate, Second Edition
> <
https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8
>
>
> <http:////
ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
> JUnit in Action, Second Edition
> <
https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22
>
>
> <http:////
ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
> Spring Batch in Action
> <
https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action
>
> <http:////
ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

sebb-2-2
On 8 November 2016 at 07:14, Romain Manni-Bucau <[hidden email]> wrote:

> Le 8 nov. 2016 07:25, "Gary Gregory" <[hidden email]> a écrit :
>>
>> On Sun, Nov 6, 2016 at 7:44 AM, Oliver Heger <[hidden email]
>>
>> wrote:
>>
>> > Hi,
>> >
>> > sorry, I don't want to stand in the way of the release. It is just that
>> > in the past we used to be very careful with artifacts deployed to Maven
>> > central and their compatibility. When I did alpha and beta releases for
>> > [configuration] 2.0 it was decided that these artifacts must not be
>> > published to Maven central because incompatibilities between succeeding
>> > alphas/betas or the final 2.0 version are likely.
>> >
>> > If the JCS betas are going to Maven central, I therefore assumed that
>> > some means were taken to deal with incompatibilities. Otherwise, if some
>> > 3rd party project has the (stupid) idea to depend on such a beta, we are
>> > in jar hell.
>> >
>>
>> That is a risk indeed. The alternatives would be:
>>
>
> This is not really valuable options IMO
>
>>  - Release betas under a beta package name
>
> Breaks more than changing almost no API - meaning of beta is "we are almost
> there".
>
>>  - Not release betas at all but just tag the software in svn/git. This
>> makes is effectively impossible to use from Maven/Ivy/AndSoOn.
>>
>
> Basically means it doesnt exist.
>
> FYI we use jcs in tomee as jcache implementation - no api risk - and needed
> to fork it to be able to release. This maybe means JCS is now no more a
> single API delivery which makes things more complex.
>
> That said, and on another topic, the rule of commons on changing packages
> shouldnt apply on alpha and beta otherwise this way of working doesnt make
> any sense anymore (= no way to get feedback since people know they will be
> fully broken anyway and not just a bit or not fully implemented).

Alpha should be used for unstable API
Beta would be for unstable Behaviour (i.e. implementation)

However I'm not sure that these should not be introduced in the middle
of a stable version series.
I would expect to find them at the start of a new major version.


>> Gary
>>
>> >
>> > Oliver
>> >
>> > Am 05.11.2016 um 23:52 schrieb Gary Gregory:
>> > > There is no need to maintain BC since 2.0 is not out. Changing package
>> > > names and Maven coordinates must also happen hand in hand. Changing
> one
>> > > means changing the other.
>> > >
>> > > Gary
>> > >
>> > > On Nov 5, 2016 1:37 PM, "Thomas Vandahl" <[hidden email]> wrote:
>> > >
>> > >> Hi Oliver,
>> > >>
>> > >> On 05.11.16 21:18, Oliver Heger wrote:
>> > >>> It seems that there are many breaking changes between this release
> and
>> > >>> beta1; for instance, the clirr report for the core component lists
>> > >>> numerous errors. Is it not against Commons policy to publish
>> > >>> incompatible artifacts with the same maven and package coordinates
> to
>> > >>> Maven central?
>> > >>
>> > >> I thought that is why we call it "beta"? It basically boils down
> again
>> > >> to the question what should be considered a public API (which btw
> hasn't
>> > >> changed since beta-1).
>> > >> I have no problem with changing the coordinates but I'm pretty sure
> that
>> > >> the next iteration to 2.0 final will introduce more incompatibilities
>> > >> and we may run out of coordinates...
>> > >>
>> > >> As I see it, we are still in the transition from 1.3
>> > >> (org.apache.jcs:jcs) to 2.0 (org.apache.commons.jcs:commons-jcs-core)
>> > >> but I'm ready to change whatever is necessary to get this out of the
>> > door.
>> > >>
>> > >> Bye, Thomas.
>> > >>
>> > >>
>> > >> ---------------------------------------------------------------------
>> > >> To unsubscribe, e-mail: [hidden email]
>> > >> For additional commands, e-mail: [hidden email]
>> > >>
>> > >>
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [hidden email]
>> > For additional commands, e-mail: [hidden email]
>> >
>> >
>>
>>
>> --
>> E-Mail: [hidden email] | [hidden email]
>> Java Persistence with Hibernate, Second Edition
>> <
> https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8
>>
>>
>> <http:////
> ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
>> JUnit in Action, Second Edition
>> <
> https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22
>>
>>
>> <http:////
> ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
>> Spring Batch in Action
>> <
> https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action
>>
>> <http:////
> ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Thomas Vandahl
On 08.11.16 10:26, sebb wrote:
> Alpha should be used for unstable API
> Beta would be for unstable Behaviour (i.e. implementation)

That is exactly what happened. JCS actually has only 3 public API
classes, JCS, CacheAccess and CacheGroupAccess. These have been
redesigned for the step from 1.3 to 2.0 but are now stable for the 2.0
API (beta1, beta2). It's all under the hood that has changed.

>
> However I'm not sure that these should not be introduced in the middle
> of a stable version series.
> I would expect to find them at the start of a new major version.

Agreed. See above. That is what happened.

Now how shall we proceed?

I'd be willing to change the groupId/package name to
org.apache.commons.jcs2 or whatever if you insist that
org.apache.commons.jcs has been wasted on 2.0-beta-1.

However, I remain to be convinced that this is the right solution for a
beta cycle.

Bye, Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

garydgregory
On Tue, Nov 8, 2016 at 9:36 AM, Thomas Vandahl <[hidden email]> wrote:

> On 08.11.16 10:26, sebb wrote:
> > Alpha should be used for unstable API
> > Beta would be for unstable Behaviour (i.e. implementation)
>
> That is exactly what happened. JCS actually has only 3 public API
> classes, JCS, CacheAccess and CacheGroupAccess. These have been
> redesigned for the step from 1.3 to 2.0 but are now stable for the 2.0
> API (beta1, beta2). It's all under the hood that has changed.
>
> >
> > However I'm not sure that these should not be introduced in the middle
> > of a stable version series.
> > I would expect to find them at the start of a new major version.
>
> Agreed. See above. That is what happened.
>
> Now how shall we proceed?
>
> I'd be willing to change the groupId/package name to
> org.apache.commons.jcs2 or whatever if you insist that
> org.apache.commons.jcs has been wasted on 2.0-beta-1.
>

I think we are good as is, keep org.apache.commons.jcs for beta2 and
eventually 2.0.

Gary


> However, I remain to be convinced that this is the right solution for a
> beta cycle.
>
> Bye, Thomas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
E-Mail: [hidden email] | [hidden email]
Java Persistence with Hibernate, Second Edition
<https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8>

<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
JUnit in Action, Second Edition
<https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22>

<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021>
Spring Batch in Action
<https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
<http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Thomas Vandahl
On 08.11.16 20:07, Gary Gregory wrote:
>> Now how shall we proceed?
>>
>> I'd be willing to change the groupId/package name to
>> org.apache.commons.jcs2 or whatever if you insist that
>> org.apache.commons.jcs has been wasted on 2.0-beta-1.
>>
>
> I think we are good as is, keep org.apache.commons.jcs for beta2 and
> eventually 2.0.

Ok, then. We would need one more PMC vote to continue. Could I please
ask for some kind soul who reviews the release candidate?

Bye, Thomas.



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Bruno P. Kinoshita-3
In reply to this post by Thomas Vandahl
+1

Built from SVN tag, with `mvn clean test site site:stage`, in following environment:

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-11T05:41:47+13:00)
Maven home: /opt/maven
Java version: 1.8.0_111, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default locale: en_NZ, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-47-generic", arch: "amd64", family: "unix"

Builds fine, all tests passing. Reports in the local staging site look good, no blockers.

Release notes look good, link to upgrade from 1.x to 2.x is working too - and users should find it useful.

Signatures from jars in staging Maven repo look good too.

Thanks
Bruno


>________________________________
> From: Thomas Vandahl <[hidden email]>
>To: Commons Developers List <[hidden email]>
>Sent: Tuesday, 1 November 2016 9:24 PM
>Subject: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2
>
>
>I would like to beta-release the [jcs] component.
>The issues found with RC1 have been addressed.
>
>Apache Commons JCS 2.0-beta-2 RC2 is available for review at:
>  https://dist.apache.org/repos/dist/dev/commons/jcs/ (r16762).
>
>Maven artifacts are at:
>  https://repository.apache.org/content/repositories/orgapachecommons-1218 .
>
>The Subversion tag is:
>
>
>https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.0-beta-2
>(r1767436).
>
>The release notes are at:
>
>
>https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.0-beta-2/RELEASE-NOTES.txt
>(r1767436).
>
>The staged site is available as a tarball at
>
>https://dist.apache.org/repos/dist/dev/commons/jcs/commons-jcs-site-2.0-beta-2.tar.gz
>(r16762).
>
>Please review the release candidate and vote.
>
>  [ ] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...
>
>Bye, Thomas
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[RESULT][VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Thomas Vandahl
In reply to this post by Thomas Vandahl
On 01.11.16 09:24, Thomas Vandahl wrote:
> I would like to beta-release the [jcs] component.

The following votes were cast (in order of appearance):

Romain Manni-Bucau: +1 (non binding)
Johannes Weberhofer: +1 (non-binding)
Gary Gregory: +1
Thomas Vandahl: +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: [hidden email]
For additional commands, e-mail: [hidden email]