Gary,
On 08.02.14 17:34, Gary Gregory wrote:
> Mat,
>
> I would suggest getting familiar with the code base in trunk. Can the code
> be released as is or are there problems? Should some issues in Jira be
> fixed for this release?
>
> Major releases like a 2.0 from 1.x are the only time APIs can
Mat,
I would suggest getting familiar with the code base in trunk. Can the code
be released as is or are there problems? Should some issues in Jira be
fixed for this release?
Major releases like a 2.0 from 1.x are the only time APIs can break binary
compatibility which means that the package name
Well I don't have experience with Apache but if you want me to help with
testing, I'm happy to do what I can. What would be most helpful?
Mat.
On 8 Feb 2014 11:38, "Thomas Vandahl" wrote:
> On 04.02.14 16:52, Gary Gregory wrote:
> > I think the biggest hurdle to releasing [JCS] 2.0 is finding a
On 04.02.14 16:52, Gary Gregory wrote:
> I think the biggest hurdle to releasing [JCS] 2.0 is finding a [Commons]
> committer willing to put in the time to go over the component and act as
> the release manager.
Well, I'm actually doing what I can. My hesitation partly comes from the
fact that the
