Release 3.0

[sne11ius]

As far as I understood, support for CMYK-Jpegs will come with 3.0. This is the main reason I would really like to see a releas soon ;)
Since I could not find a maven repo containing 3.0-SNAPSHOT, I will now have to build my own and deploy to our internal nexus...

[haraldk]

Hi Cornelius,

Thanks for your interest! To be honest, I'd like to see a release soon myself. :-)

The only reason I haven't made one yet, is time. I'd like to spend more time on the project, but currently I'm doing everything on my spare time, which unfortunately, isn't much.

If you like to help out, in setting up proper release management and find a proper repository, we could probably create a release candidate at least (or even snapshots), to ease development. I know this would make several people
happy.

Best regards,

Harald K

[sne11ius]

I'll ask my employer to allow me to spend some time on this. I think the chance is somewhere close (but still above) zero ;)

[ankon]

I just found this library, it's great. Having a 3.0 release would be awesome :)

I might also be able to help out to reach that goal, as it would remove the need for keeping private builds in our private repository.

[sne11ius]

Ok, let's have a tiny discussion of what needs to be done:

1. Handle the (currently) two Pull-Requests somehow
2. Triage the various forks here on github and reintegrate appropriate (wanted) changes
3. Prepare the release:
   1. Create a github milestone and assign the issues to it
   2. Update the pom.xml
   3. Tag the release
4. Find out how to release to maven central (http://maven.apache.org/guides/mini/guide-central-repository-upload.html might be a good start, I'm totally new to publicly releasing maven artifacts)
5. Do it!

Questions/Suggestions I have:

1. Do we need release candidates? I suggest we do a RC1 and (if no issues come up) go to the release version from there.
2. @haraldk as far as I understand, there is also a project at java.net. Do you consider the github project the "main" one? If so, it might make sense to put a big "This project moved..."-notice on the frontpage of the java.net project. The current notice only mentions "Source code", not the project itself and is also quite small ;)
3. I think it makes sense to create some kind of release plan in the wiki and that would be my next action.

Wdyt? All comments welcome ;)

[haraldk]

All right!

I see you have already started your work, and that's cool. I just started christmas holidays with my family, but I'll try to help out as much as I can.

TODOs:

• I've been working on improved JPEG writing (CMYK write support) and TIFF writing for some time. I don't have issues in the tracker for these, but I could add them for the transparency of the project. But these changes won't make it into 3.0 if we are to release a 3.0 this year. Let's schedule them for 3.1.
  • I have some changes in the servlet-module that I made long time ago but didn't push. I think I'll do that, as they should go into 3.0 release.

Suggestions:

1. If we make an RC, please make it RC5 (I've created a few semi-official RCs already...). :-) But I'm fine with building 3.0 release.
2. Agree about the java.net part. I don't think it has a purpose anymore. I'll try to log in and update the page.

.k

[sne11ius]

Personally, I don't really need the 3.0 to come in 2013, since I won't have much time during the holidays anyways.
If you think your JPEG & TIFF writing improvements could make it into the new version with some help (maybe in the beginning of 2014) let me know. Maybe I can work on the code a little.

[haraldk]

The changes in JPEG & TIFF writing is currently in my local branch only, but I could push the JPEG part at least. There's a couple of unit tests with @Ignore that should demonstrate the known issues.

PS: The java.net project is updated. Unfortunately, there's very limited formatting capabilities. But at least it's a little better now. Let me know if you have suggestions on how to make it clearer.

PPS: Last time I was looking into release, I considered using Sonatype (https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide ), but I don't have any preferences at this point. I'll read up on both Sonatype and Apache. :-)

.k

[haraldk]

Quick update: Sonatype repo is in the works. Hopefully we'll have an RC out before the end of the week.

[thaichat04]

We are impatient to have this release :)

[trygvis]

FYI. 3.0-rc5 is out.

[haraldk]

Thank you @trygvis! :-)

[marcuslinke]

Great news! Thank you guys!

[marcuslinke]

...but there is no tag/branch...

[trygvis]

It's here: https://github.com/trygvis/TwelveMonkeys

Hopefully @haraldk will be able to do the release next time.

[marcuslinke]

Hmm. OK. So it would make sense to merge that tag here, right @haraldk ?

[haraldk]

@marcuslinke Yes! Done. :-)

I've merged @trygvis' changes, so the tag should be there.

Harald K

[marcuslinke]

@haraldk Seems tags are not pulled. Did you

git fetch --tags

?

[haraldk]

Dang..

No. All I did was:

git pull https://github.com/trygvis/TwelveMonkeys master

...and pushed the merged result + more commits later...

I thought that would do the trick, but apparently not. Is it too late to fetch/apply tags now, or is it possible to get it right still? :-)

(sorry for being a Git n00b at times... :-P)

I guess as a worst case, I could create a new RC, and test the release
process while we're at it...

Harald K

[haraldk]

Update. Tag is there. :-)

Harald K

[marcuslinke]

Good news after coming from vacation. Thanks @haraldk

[stozlu]

I'm also looking forward to 3.0 release. This will fix a lot of issues we're having with customer images.

[haraldk]

...and there! Finally!

To all who have waited: Thank you for your patience! :-)

TwelveMonkeys 3.0

Best regards,

Harald K

[thaichat04]

Got it from Maven Centra. Great work !

Thank