Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [egit-dev] Plan for upcoming releases
On Sat, Sep 14, 2013 at 7:25 PM, David M Williams <david_williams@xxxxxxxxxx> wrote:
> 3.1.0:  Oct 2, 2013 (Luna M2)

Friendly reminder that your Luna contribution in b3aggrcon file still says .../egit/updates-3.0.1
That is, it is "less than" what is in your Kepler SR1 contribution file.

it's not 3.0.2 since the aggregation build on Kepler SR1 RC3 revealed that we miss some legal
files in the source bundles. Hence I didn't declare this build to be final. I'll hope to fix this today
and then update both our Kepler SR1 and Luna contribution to 3.0.2. 

We only maintain one stable build which currently still is dedicated to  3.0.2 until that's final. 
Currently our nightly build has 3.1.0-SNAPSHOT. I'll fork master to stable-3.1 branch
around Wednesday and then reconfigure the stable builds to care for 3.1.-SNAPSHOT. After this happened
I will update our Luna contribution to something 3.1.0-ish.
 
While it is true you do not HAVE to be up to date in Luna until your +n day, I always think its a good idea to
update the file "incrementally" ... as soon as you have anything from 3.1.0 stream to contribute, even if it is not final,
it can help find problems early ... especially when you are working towards a new release or changing minor versions.

I noticed this because I wanted to update our "pre-req" in our Platform build and wasn't sure what to update it to, so checked
your b3aggrcon file.  
We just have only a "small" dependency due to an optional unit test we do for "copyright tool" (and need it only for building, we don't re-distribute it, or anything ... but, our M2 is quite soon, so I
wanted to 'be close' to what ever your final M2 contribution would be ... any advice?
If so, feel free to comment in bug 417267.
                 https://bugs.eclipse.org/bugs/show_bug.cgi?id=417267

Thanks,




From:        Matthias Sohn <matthias.sohn@xxxxxxxxx>
To:        Chris Aniszczyk <caniszczyk@xxxxxxxxx>,
Cc:        EGit developer discussion <egit-dev@xxxxxxxxxxx>, JGit Developers list <jgit-dev@xxxxxxxxxxx>
Date:        09/12/2013 03:53 PM
Subject:        Re: [egit-dev] [jgit-dev]  Plan for upcoming releases
Sent by:        egit-dev-bounces@xxxxxxxxxxx



ok, let's plan to ship 3.2 with Kepler SR2
I updated the project plans accordingly

On Thu, Sep 12, 2013 at 5:35 PM, Chris Aniszczyk <caniszczyk@xxxxxxxxx> wrote:
My preference is 3.2.0


On Wed, Sep 11, 2013 at 6:59 AM, Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:
good question, according to [1] we can ship a minor release with a SR if the minor
release was released 1 month before the RC1 of the SR, for Kepler SR2 this means
we would have to release before Christmas (Dec 24), this means we could ship 3.2.0.

So we have the option to either ship 3.2.0 or 3.0.3 with Kepler SR2. 
Opinions ?

--
Matthias

[1] http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg09529.html



On Wed, Sep 11, 2013 at 1:33 PM, Mikaël Barbero <mikael.barbero@xxxxxxxxx> wrote:
Hi Matthias,

What is the plan regarding Kepler SR2? Will it be 3.2.0 from Luna M4 or 3.0.3?

Regards,
Mikael

Le 11 sept. 2013 à 13:01, Matthias Sohn <matthias.sohn@xxxxxxxxx> a écrit :

I have setup a tentative release schedule until Luna:

3.1.0:  Oct 2, 2013 (Luna M2
3.2.0:  Dec 18, 2013 (Luna M4)
3.3.0:  Feb 28, 2014 (Luna M6)
4.0.0:  June 25, 2014 (Luna)

and added a tentative plan until 4.0.0 here
https://projects.eclipse.org/projects/technology.jgit/releases/4.0.0
https://projects.eclipse.org/projects/technology.egit/releases/4.0.0
this draft lists new features already cooking in Gerrit and those I know we
at SAP plan to work on.

Committers feel free to update the plan with features you plan to implement until Luna.
Add a hint until which release you plan the feature to be ready.

Contributors let us know if you want to see cool new features you plan to implement
until Luna in the project plan.

--
Matthias
___________________________________________ ____
egit-dev mailing list
egit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/egit-dev



___________________________________________ ____
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
_________________ _________________________ _____
egit-dev mailing list
egit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/egit-dev

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


Back to the top