ship JGit and EGit 3.1 with Kepler SR1 since RC1 already passed.
Hence I propose we ship a pure maintenance release 3.0.x with SR1
and ship 3.1 independently of the release train through our own
Speak up if you have a different proposal.
Any changes which should go with the maintenance release for SR1
need to be pushed for branch stable-3.0. If there are new patches
on this branch I will simply create 3.0.x maintenance releases for
the RCs for SR1, find the SR1 schedule here . Last build for SR1
is on Sept 18 (we are in +3 slot of the schedule).
Let me know if there are any important patches which already reached
master which you want also on 3.0.x.
I plan to release 3.1 shortly after Kepler SR1 (around end of September)
in order to avoid overloading on my end ;-)
This will also help to avoid that we need multiple release build
jobs in parallel.