commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2
Date Tue, 08 Nov 2016 09:26:04 GMT
On 8 November 2016 at 07:14, Romain Manni-Bucau <rmannibucau@gmail.com> wrote:
> Le 8 nov. 2016 07:25, "Gary Gregory" <garydgregory@gmail.com> a écrit :
>>
>> On Sun, Nov 6, 2016 at 7:44 AM, Oliver Heger <oliver.heger@oliver-heger.de
>>
>> 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" <tv@apache.org> 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: dev-unsubscribe@commons.apache.org
>> > >> For additional commands, e-mail: dev-help@commons.apache.org
>> > >>
>> > >>
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> > For additional commands, e-mail: dev-help@commons.apache.org
>> >
>> >
>>
>>
>> --
>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>> 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: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message