[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mat-dev] A few updates ...
|
Hi,
just a short update on the current release preparation:
- I just contributed the results from today's MAT build to Luna RC2. Andrew fixed an issue with the Acquire functionality in the RC1 candidate [1]. Thanks, Andrew!
- Checked all the compliance reports of the Luna RC1 and found no issues related to MAT.
- The IP Log for the 1.4.0 release is approved
- I updated the review documentation in the PMI [2] and asked yesterday the on the Tools PMC mailing list for approval. We just got a +1 while I was typing this message :)
- There is still some work needed to produce the standalone packages with the correct notice.html (I am looking into it)
Krum
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=435585
[2] http://projects.eclipse.org/projects/tools.mat/releases/1.4.0/review
-----Original Message-----
From: mat-dev-bounces@xxxxxxxxxxx [mailto:mat-dev-bounces@xxxxxxxxxxx] On Behalf Of Tsvetkov, Krum
Sent: Mittwoch, 21. Mai 2014 09:28
To: Memory Analyzer Dev list
Subject: [mat-dev] A few updates ...
Hi,
Here are some updates on MAT.
Upcoming Release (participation in Luna):
----------------------------------------------------
- Today I am going to make MAT's contribution to Luna RC1. From the code side I think we are ready for the release and if we don't find a very critical issue, then todays contribution will be the one we release with Luna
- MAT's chart feature is still disabled in the simultaneous release, because of missing BIRT [1]. I hope this will change with RC1.
- I still have some issues building the standalone MAT installations - last release we made with binaries from Indigo, which is already very old, therefore we will do this year's release with (at least) Kepler binaries [2]. However, the notice.html in the root is then the one from Kepler, and it doesn't have the small change made this year. Therefore I will try to produce standalone packages with Luna. To do this, I will have to produce the packages not as part of our normal the plugins build, but later:
* build our plugins for the Luna release (hopefully todays RC1 state)
* wait until the final Luna repo is ready
* run a build which packages our released plugins / features with the release ready Luna parts
If this doesn't work, we will fall back to using Kepler, and I will change the notice.html files manually once in all the zip files
- Deadline for submitting the IP log is this Friday. I just tried to submit it and faced an issue - currently all committers are listed as "never active". I opened a bug for this [3]
After Luna:
----------------------------------------------------
SVN was officially deprecated recently [4]. Therefore MAT is also going to move to GIT after the Luna release.
Krum
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=432464 Temporary disabled BIRT, MAT, and Stardust for Luna warm up builds
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=427081 Create stand-alone MAT based on Kepler (4.3)
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=435355 All committers on tools.mat are listed as never active
[4] https://dev.eclipse.org/mhonarc/lists/eclipse.org-committers/msg00947.html
_______________________________________________
mat-dev mailing list
mat-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mat-dev
