Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[mat-dev] RE: MAT Development after the 1.0.0 Release

Hi,

 

Here a short update from me. The fixing of bugs for our bug-fix release is going pretty good. Here a summary of Bugzilla messages which have been closed, and of what is left.

 

Closed bugs:

 

312594: SnapshotImpl instance kept by ExecutionJob after closing the editor

https://bugs.eclipse.org/bugs/show_bug.cgi?id=312594

 

313475: New GC root types make Paths from GC roots and Dominator tree less expressive

https://bugs.eclipse.org/bugs/show_bug.cgi?id=313475

 

314552: IndexOutOfBoundsException parsing IBM core dump

https://bugs.eclipse.org/bugs/show_bug.cgi?id=314552

 

315940: Remember custom JDK that is set for Acquire Heap Dump

https://bugs.eclipse.org/bugs/show_bug.cgi?id=315940

 

312035: Copyright meta-data in the HTML Documentatio pages generated by DITA is wrong

https://bugs.eclipse.org/bugs/show_bug.cgi?id=312035

 

313923: Copy-paste on a large set takes an extremely long time

https://bugs.eclipse.org/bugs/show_bug.cgi?id=313923

 

317278: org.eclipse.mat.ui.help contains empty src/org.eclipse.mat.ui folder

https://bugs.eclipse.org/bugs/show_bug.cgi?id=317278

 

317446: Handle huge array sizes

https://bugs.eclipse.org/bugs/show_bug.cgi?id=317446

 

Won’t fix for 1.0.1

 

315283: Acquire head dump dialog: set a warning when the file already exists

https://bugs.eclipse.org/bugs/show_bug.cgi?id=315283 – Although I initially proposed that this one should be fixed, after looking into it again I found that it requires some more thinking before changing anything and we decided to leave it for now and consider it again for a next release.

 

Things which need to be finished:

 

* 318288: The ParseHeapDump script doesn't run on AIX

https://bugs.eclipse.org/bugs/show_bug.cgi?id=318288Initial fixes are done, now Andrew is additionally preparing a script specific for AIX 64 bit

 

* 312623: RCP Solaris x86_64

https://bugs.eclipse.org/bugs/show_bug.cgi?id=312623 – the published RCP for Solaris on x86 is missing some bundles. We need to fix this. It will be done as part of the next point:

 

* Build MAT RCPs with Maven/Tycho – as stated last time we would like to focus on one build job only, and have chosen the maven/tycho one. We are working on getting the RCPs build with it.

 

* Testing – Once we get the RCPs to build on build.eclipse.org (the point above) we should spend reasonable time testing that everything is as expected on the different platforms.

 

Krum

 

Krum Tsvetkov
www.sap.com

http://www.sap.com/company/legal/impressum.epx

 


From: mat-dev-bounces@xxxxxxxxxxx [mailto:mat-dev-bounces@xxxxxxxxxxx] On Behalf Of Tsvetkov, Krum
Sent: Freitag, 18. Juni 2010 11:02
To: Memory Analyzer Dev list
Subject: [mat-dev] MAT Development after the 1.0.0 Release

 

Hi,

 

Some days ago we went through the Bugzilla entries with Andrew and had a discussion on the next steps after the 1.0.0 release is out and our contribution to Helios is done. This is the current proposal. Feedback is appreciated.

 

1) Plan for next releases

1.0.1 – we should work on some of the bugs which were recently reported for 1.0 or which we haven’t fixed before and publish shortly a bugfix release 1.0.1

1.1.0 – we should stick to the Helios SPs time schedule and try to do a 1.1 release with SP1 (September)

 

2) Development code line

For the 1.0.0 release there is a tag in SVN, so far we haven’t branched anything. The idea is to continue to work in trunk for the moment and do only fixes needed for the bugfix release

 

3) API tooling

Please enable the API tooling and use the 1.0.0 version from 20 May as a baseline. We should make sure that there are no API changes in the bugfix release.

 

4) Bugs to be fixed for 1.0.1 (proposal)

These seemed to be bugs that we have to solve shortly, or looked as bugs that we can solve shortly. If some of the changes requires some refactoring or too-much effort we should leave it for the next release.

 

312594: SnapshotImpl instance kept by ExecutionJob after closing the editor

https://bugs.eclipse.org/bugs/show_bug.cgi?id=312594

 

312623: RCP Solaris x86_64

https://bugs.eclipse.org/bugs/show_bug.cgi?id=312623

 

313475: New GC root types make Paths from GC roots and Dominator tree less expressive

https://bugs.eclipse.org/bugs/show_bug.cgi?id=313475

 

314552: IndexOutOfBoundsException parsing IBM core dump

https://bugs.eclipse.org/bugs/show_bug.cgi?id=314552

 

315283: Acquire head dump dialog: set a warning when the file already exists

https://bugs.eclipse.org/bugs/show_bug.cgi?id=315283

 

315940: Remember custom JDK that is set for Acquire Heap Dump

https://bugs.eclipse.org/bugs/show_bug.cgi?id=315940

 

312035: Copyright meta-data in the HTML Documentatio pages generated by DITA is wrong

https://bugs.eclipse.org/bugs/show_bug.cgi?id=312035

 

313923: Copy-paste on a large set takes an extremely long time

https://bugs.eclipse.org/bugs/show_bug.cgi?id=313923

 

317278: org.eclipse.mat.ui.help contains empty src/org.eclipse.mat.ui folder

https://bugs.eclipse.org/bugs/show_bug.cgi?id=317278

 

5) Outlook for 1.1

Here are some things that require more effort than the bugfixing, and we would like to do it for the next release. If we can manage this is another question J

 

268458: Support and expose stackframe information provided by java 6 update >= 14 and java 7

https://bugs.eclipse.org/bugs/show_bug.cgi?id=268458

 

271908: histogram comparison view simple enhancements

https://bugs.eclipse.org/bugs/show_bug.cgi?id=271908

 

298078: Comparison Features in MAT

https://bugs.eclipse.org/bugs/show_bug.cgi?id=298078

 

272318: add 'expand all' and 'collapse all' actions to trees

https://bugs.eclipse.org/bugs/show_bug.cgi?id=272318

 

296826: Detect cycles in WeakHashMaps

https://bugs.eclipse.org/bugs/show_bug.cgi?id=296826

 

302934: Hash Entries Query doesn't work for ConcurrentHashMap

https://bugs.eclipse.org/bugs/show_bug.cgi?id=302934

 

6) Update project plan

I will take care to reflect these in the project metadata (currently there is not next release described there) and in the project plan.

 

7) Build

Currently we still have two build jobs at builds.eclipse.org. I think it makes sense to focus on one build/build technology, make it stable, and make it do all we need. We will focus on the maven/tycho build and try to get it in a good shape.

Krum Tsvetkov
www.sap.com

http://www.sap.com/company/legal/impressum.epx


Back to the top