You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Mark Roberts <ma...@cs.washington.edu> on 2015/08/12 23:43:30 UTC
RE: [BCEL] 6.0 RC4
I would like to update some of my proposed fixes and lobby for their inclusion in the next release of BCEL. To that end I presume I should be comparing my changes with the source in the RC4 tag as opposed to the trunk. Is that correct?
Thank you,
Mark Roberts
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [BCEL] 6.0 RC4
Posted by Gary Gregory <ga...@gmail.com>.
Hi Mark,
We all work here as volunteers, and as such, time and interest can be
limited or focused on specific Commons components and areas. It's really
just up to one of us (any Apache committer or a PMC member) to put in the
time.
In general, providing patches with unit tests is the best way to get an
issue resolved.
Pinging the ML helps too ;-)
As you might have noticed, we just had a 6.0 RC that failed and has been
followed by a flurry of commits from several different devs.
I would make sure all of your patches can be applied cleanly on top of
trunk. I know it might be a pain, but it's the best way.
It looks like we have an RM that is willing to put in the time to shepherd
a release.
If your changes break BC, then now is time to try to get them in.
Gary
On Thu, Aug 13, 2015 at 10:45 AM, Mark Roberts <ma...@cs.washington.edu>
wrote:
> (Thank you - I will use the trunk.)
>
> I have about 10 open issues that have received no comments or attention
> (that I am aware of) in the last 6 months or so. As I noted in my
> introduction (attached) several of our release tools use the BCEL library
> for class file manipulation. We continue to release updates every month
> and it would be nice to have our changes adopted so that we can release an
> 'official' BCEL, rather than our private branch. To that end, I am unclear
> as to the procedure used to decide what is (or is not) included in a
> release. I certainly have time available to help out. Is there some way
> I can be of more assistance in this process?
>
> Thank you,
> Mark
>
> -----Original Message-----
> From: Gary Gregory [mailto:garydgregory@gmail.com]
> Sent: Thursday, August 13, 2015 8:17 AM
> To: Commons Developers List
> Subject: Re: [BCEL] 6.0 RC4
>
> I would work against the latest from trunk.
>
> Gary
>
> On Wed, Aug 12, 2015 at 2:43 PM, Mark Roberts <ma...@cs.washington.edu>
> wrote:
>
> > I would like to update some of my proposed fixes and lobby for their
> > inclusion in the next release of BCEL. To that end I presume I should
> > be comparing my changes with the source in the RC4 tag as opposed to
> > the trunk. Is that correct?
> >
> > Thank you,
> > Mark Roberts
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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 <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
>
>
> ---------- Forwarded message ----------
> From: Mark Roberts <ma...@cs.washington.edu>
> To: "'Commons Developers List'" <de...@commons.apache.org>
> Cc:
> Date: Fri, 23 Jan 2015 12:55:15 -0700
> Subject: [bcel] new to list - introduction
> My name is Mark Roberts and I work in the Programming Languages and
> Software
> Engineering group (PLSE) at the University of Washington.
> (http://www.cs.washington.edu/research/plse)
>
> Our team develops and supports a number of open source tools. One of the
> main ones, Daikon (http://plse.cs.washington.edu/daikon/) makes extensive
> use of BCEL to manipulate Java class files. We have been using BCEL since
> 2001 and have made a few changes along the way. I have just completed
> re-merging our BCEL source tree with a fairly recent mainline version
> (r1646789 2014-12-19).
>
> I have exchanged email with Torsten Curdt and he suggested I join this
> mailing list as a first step in sharing our changes and fixes.
>
> Thank you,
> Mark
>
>
>
>
> ---------------------------------------------------------------------
> 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
<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
RE: [BCEL] 6.0 RC4
Posted by Mark Roberts <ma...@cs.washington.edu>.
(Thank you - I will use the trunk.)
I have about 10 open issues that have received no comments or attention (that I am aware of) in the last 6 months or so. As I noted in my introduction (attached) several of our release tools use the BCEL library for class file manipulation. We continue to release updates every month and it would be nice to have our changes adopted so that we can release an 'official' BCEL, rather than our private branch. To that end, I am unclear as to the procedure used to decide what is (or is not) included in a release. I certainly have time available to help out. Is there some way I can be of more assistance in this process?
Thank you,
Mark
-----Original Message-----
From: Gary Gregory [mailto:garydgregory@gmail.com]
Sent: Thursday, August 13, 2015 8:17 AM
To: Commons Developers List
Subject: Re: [BCEL] 6.0 RC4
I would work against the latest from trunk.
Gary
On Wed, Aug 12, 2015 at 2:43 PM, Mark Roberts <ma...@cs.washington.edu>
wrote:
> I would like to update some of my proposed fixes and lobby for their
> inclusion in the next release of BCEL. To that end I presume I should
> be comparing my changes with the source in the RC4 tag as opposed to
> the trunk. Is that correct?
>
> Thank you,
> Mark Roberts
>
>
>
>
>
>
> ---------------------------------------------------------------------
> 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 <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
Re: [BCEL] 6.0 RC4
Posted by Gary Gregory <ga...@gmail.com>.
I would work against the latest from trunk.
Gary
On Wed, Aug 12, 2015 at 2:43 PM, Mark Roberts <ma...@cs.washington.edu>
wrote:
> I would like to update some of my proposed fixes and lobby for their
> inclusion in the next release of BCEL. To that end I presume I should be
> comparing my changes with the source in the RC4 tag as opposed to the
> trunk. Is that correct?
>
> Thank you,
> Mark Roberts
>
>
>
>
>
>
> ---------------------------------------------------------------------
> 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
<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