commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Damjan Jovanovic <>
Subject Re: [imaging] Plan for 1.0.0 release
Date Mon, 21 Oct 2013 13:47:31 GMT
Well as the only committer that's really working on the internals, I
am wondering what to do myself now.

I've been working on (and have almost finished) a very large change
affecting virtually everything. When I commit it, the API will come
apart at the seams :-/, and people will not be very happy with the
rewrites of their own code they'll be doing.

Which of the following would be best:
1. Releasing what is in SVN trunk now (maybe minus another API
breaking change from a few months ago) as 1.0, then adding my large
API-breaking change which will eventually be released as version 2.0.
2. Adding my large change now and API-breaking everything in trunk,
then releasing that as 1.0.
3. Releasing what is in SVN trunk now (maybe minus another API
breaking change from a few months ago) as 0.98, then API-breaking
everything, and then either releasing a 0.99 or 1.0. (This is probably
the hardest option, and may not be possible, since version numbering
of nightly builds will go backwards and JIRA bugs will need to be

Thoughts? Preferences?


On Mon, Oct 21, 2013 at 3:30 PM, Raul Kripalani <> wrote:
> Hello all,
> Are there any plans for releasing 1.0.0 soon?
> The last commit was 2 months old and the community will hands-down benefit
> from a GA release that includes the bugfixes and code renames from Sanselan
> to Commons Imaging, carried out ever since 0.9.7.
> Can I help in any way? We need the 1.0.0 release for our project to acquire
> the fix for IMAGING-49 [1], and we cannot rely on SNAPSHOTs.
> [1]
> Thanks,
> *Raúl Kripalani*
> Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
> Integration specialist
> |
> | twitter: @raulvk

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message