Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mat-dev] Memory Analyzer 1.15.0
Hi team,

Thank you for all your work on this project.
As a lurker who has not yet contributed, yes I believe Andrew's ideas #6 ( keyword=’helpwanted’ ) and #8 (documentation on how to help) would be valuable to me.
Direct recommendations on how I can help are also appreciated. I have experience writing a standalone plugin using MAT API, but have not yet touched the core tool.

Best,
Daniel 

On Wed, Sep 20, 2023 at 8:11 AM Andrew Johnson via mat-dev <mat-dev@xxxxxxxxxxx> wrote:

I think we should plan for a new release of Memory Analyzer.

 

There is a placeholder target field 1.15.0 for Git which I have used for some of the current defect / features.

https://bugs.eclipse.org/bugs/buglist.cgi?classification=Tools&list_id=21370820&product=MAT&query_format=advanced&target_milestone=1.15.0

The full unresolved bug and enhancement list is:
https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;order=Importance;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;product=MAT


I was thinking of December 2023, to coincide with SimRel 2023-12. Does that give enough time for us, and is that soon enough for users?

 

Other things to do might be:

  1. Check how MAT works with Java 21 (LTS), from OpenJDK, Temurin and Semeru (when available), for running with, and analysing dumps from.
  2. Check we are up to date on dependencies, to avoid security warnings.
  3. Write a release record at the project page. https://projects.eclipse.org/projects/tools.mat
  4. Follow https://wiki.eclipse.org/MemoryAnalyzer/Contributor_Reference#New_version_development_process
  5. Follow https://wiki.eclipse.org/MemoryAnalyzer/Contributor_Reference#Simultaneous_release_policies

 

I know that no one is working full time on the project – but how and for what can we encourage help from others?

  1. Documentation – it’s in DITA which might be a bit unclear but is sort of like HTML.
    1. Do we need an explanation and images of all the views?
    2. The acquiring a heap dump section needs updates for more recent version of Java.
  2. Build – is there a Tycho / Maven person who could review our build process? Can we get a dependency check for vulnerabilities, or a software bill of materials?
  3. Translations – does anyone want MAT translated to another language. MAT is enabled, and translations updates can be made via https://babel.eclipse.org/ and the results can be installed into MAT. However, all the translations are incomplete, and the best, Japanese, is only 33% translated. We would need people fluent in the target language who also understand English and MAT well.
  4. Do we need an automated regression test build?
  5. Do we need an automated performance test build?
  6. Should we tag some bugs with keyword=’helpwanted’ ?
  7. How well do the ‘Leak Suspects’ and ‘Top Components’ reports work for users? Do they actually show the problems?
  8. Do we need a section on the website explaining how to help the project?

 

Thoughts, anyone,

 

Andrew Johnson

Unless otherwise stated above:

IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
_______________________________________________
mat-dev mailing list
mat-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mat-dev


--
Daniel DeVeau
Manager, Solution Engineering, Appian
Appian.com | daniel.deveau@xxxxxxxxxx

--
This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use, or distribution of the information included in this message is prohibited -- please immediately and permanently delete this message.

Back to the top