Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jgit-dev] [egit-dev] Fwd: [cross-project-issues-dev] Announcing participation in Neon
I now published to the cross-projects list that we will ship 5.0 with Neon and created corresponding
release records in the project portal


We will evolve the plan content as we go forward, please mark bugs you plan to implement
in 4.3 or 5.0 with the respective milestone in Bugzilla, Then they will show up in the issue
list of the corresponding release record in the project portal.
I have created milestone versions 4.3 and 5.0 for that.

In case we find later that we have no breaking changes we can rename the release we ship with Neon from 5.0 to 4.4


On Tue, Oct 27, 2015 at 1:19 PM, Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:
so far in most years we did quarterly minor releases and a major release in June if we had breaking changes.
Micro releases we did ad-hoc when we fixed severe bugs. Micro releases do not require neither
IP nor release review so it's not a lot of work to create them.

-Matthias


On Tue, Oct 27, 2015 at 11:28 AM, Andrey Loskutov <loskutov@xxxxxx> wrote:
Hi Matthias,
Sounds good.
 
Do I get it right: we don't plan to ship "micro" releases in between and instead just work mostly on one branch, creating "minor" version bumps if needed?
 
Kind regards,
Andrey Loskutov

http://google.com/+AndreyLoskutov
 
Gesendet: Dienstag, 27. Oktober 2015 um 10:11 Uhr
Von: "Matthias Sohn" <matthias.sohn@xxxxxxxxx>
An: "JGit Developers list" <jgit-dev@xxxxxxxxxxx>, "EGit developer discussion" <egit-dev@xxxxxxxxxxx>
Betreff: [egit-dev] Fwd: [cross-project-issues-dev] Announcing participation in Neon
I announced participation of JGit and EGit in the Neon release train which will be shipped June 2016 [1]
 
We still have to decide which version we want to ship in June 2016.
 
I propose we continue the scheme we followed the last years:
- release 4.2 in Dec 2015
- release 4.3 in Mar 2016
- release 5.0 in June 2016 to allow for API breaking changes (if there are no API breaking changes
                     we can release 4.4 instead)
 
Opinions, thoughts on this proposal ?
 
-Matthias


Back to the top