|Re: [tracecompass-dev] Trace Compass 2.1/Neon.1 RC1 posted|
From my point of view I'm ok to add it to 2.1. Please cherry-pick it to stable-2.1 branch.
Do you have to update the minimum version in the code as well? Not sure if it has been done with these patches.
Could you also add note to the release notes for this?
I have added https://git.eclipse.org/r/#/c/
79968/for 2.1, which was just merged into master. It finalizes the support for the LTTng-Analyses 0.5 (and LAMI 1.0 spec), the rest of the support was already in. It would be great if this could go in for 2.1, as it will make Trace Compass compatible with the latest versions of LTTng-Analyses.
On 2016-08-24 03:42 PM, Bernd Hufmann wrote:
I posted the Trace Compass 2.1/Neon.1 RC1 build:
It is based on commit:7a65e099d459077e5c364dd
I've also created the release branch stable-2.1.
Trace Compass 2.1/Neon.1 RC2 build will be Wednesday, August 31st, 2016.
- RC1 is API and feature freeze for this release.
- For any fixes that need to go into the 2.1 release, please provide a patch on master first and then cherry-pick it on stable-2.1 branch after it's merged to master.
tracecompass-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Back to the top