commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benedikt Ritter <brit...@apache.org>
Subject Re: [VOTE] Release BCEL 6.0 based on RC3
Date Thu, 19 Feb 2015 06:45:39 GMT
2015-02-19 5:11 GMT+01:00 Gary Gregory <garydgregory@gmail.com>:

> On Wed, Feb 18, 2015 at 7:04 PM, Ben McCann <ben@benmccann.com> wrote:
>
> > Would it be possible to release 6.0 now and release Mark's patches as 6.1
> > or 7.0? I'm concerned it may be quite a long time before his patches are
> > committed since they are not actively being reviewed and there is no
> > activity on them for the past couple weeks.
> >
> > There is little downside to frequent releases in my experience.
> Infrequent
> > releases on the other hand can be a source of frustration as it means it
> > can be quite difficult to use the code that has been committed.
>
>
> +1
>

If those changes don't imply breaking binary compatibility we can include
them in 6.1.


>
> Gary
>
>
> > This is the
> > exact reason the node.js community was splintered and the io.js fork was
> > created. While end users can easily build from source it can become
> > extremely difficult when there are multiple transitive dependencies
> relying
> > on the library. Users end up having to maintain patched versions not only
> > of BCEL but of the libraries that depend on BCEL which means there can be
> > quite a bit of overhead. As the length of time between releases grows the
> > number of custom patches each user has to separately maintain in each
> > library depending on BCEL grows. Right now it has been nine years.
> >
> > Thanks,
> > Ben
> >  On Feb 10, 2015 1:53 AM, "Ben McCann" <ben@benmccann.com> wrote:
> >
> > > Great, thanks for the update!
> > >
> > > Btw, for those not familiar with which issues those are, here's a list
> of
> > > the ones Mark raised that are not yet resolved:
> > > https://issues.apache.org/jira/browse/BCEL-79
> > > https://issues.apache.org/jira/browse/BCEL-195
> > > https://issues.apache.org/jira/browse/BCEL-196
> > > https://issues.apache.org/jira/browse/BCEL-197
> > > https://issues.apache.org/jira/browse/BCEL-198
> > > https://issues.apache.org/jira/browse/BCEL-199
> > > https://issues.apache.org/jira/browse/BCEL-200
> > > https://issues.apache.org/jira/browse/BCEL-201
> > > https://issues.apache.org/jira/browse/BCEL-202
> > > https://issues.apache.org/jira/browse/BCEL-205
> > > https://issues.apache.org/jira/browse/BCEL-206
> > > https://issues.apache.org/jira/browse/BCEL-208
> > > https://issues.apache.org/jira/browse/BCEL-209
> > >
> > > Thanks!
> > > -Ben
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Sun, Feb 8, 2015 at 11:32 PM, Emmanuel Bourg <ebourg@apache.org>
> > wrote:
> > >
> > >> Le 09/02/2015 06:29, chengas123 a écrit :
> > >>
> > >> > BCEL really needs the 6.0 release to be cut or it will no longer be
> > >> > compatible with any supported version of Java. Would anyone be able
> to
> > >> cut a
> > >> > new release?
> > >>
> > >> I will once the issues raised by Marks Roberts are addressed.
> > >>
> > >> Emmanuel Bourg
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > >> For additional commands, e-mail: dev-help@commons.apache.org
> > >>
> > >>
> > >
> > >
> > > --
> > > about.me/benmccann
> > >
> >
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition
> <http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message