[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jgit-dev] do we want to release 4.0 or 3.4 in June ?

The m2e EGit scm provider uses a version range eg [3,4) so knock on effects with versions can cause problems. Unless there's a really good reason to raise the major version I would recommend that it isn't raised. 

Alex

Sent from my iPhone 5

On 21 Feb 2014, at 14:32, Chris Aniszczyk <caniszczyk@xxxxxxxxx> wrote:

3.4 seems fine since nothing is breaking, worst case scenario, if we want to do something that breaks changes it's easier to go to 4.0 then the other way around :)

Thanks for doing the release work again!


On Thu, Feb 20, 2014 at 4:48 PM, Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:
When we put together the plan for 4.0 (Luna timeframe) we were assuming
we might need to break API e.g. for supporting symlinks or interactive rebase
but it seems we found a way to avoid breaking the API. I am not aware of any
breaking changes in review for our Luna release in June.

I think if that's true we should change the plan and release 3.4 instead of 4.0 for
Luna. Speak up if you have any breaking changes you'd like to include in our
next release after 3.3.

--
Matthias


_______________________________________________
jgit-dev mailing list
jgit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jgit-dev




--
Cheers,

Chris Aniszczyk
http://aniszczyk.org
+1 512 961 6719
_______________________________________________
jgit-dev mailing list
jgit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jgit-dev