We intend to create the tag (or branch) for
the “old” 8.0 release next weak on Tuesday. We would put then this version on
the update site as the latest 8.0 build.
Then we will continue in trunk the
development of what would be the 1.0 release, meaning there will be some bigger
changes introduced.
Are there any objections to do the split
on Tuesday (19 Jan) – may be some unfinished fixes expected in 0.8?
From:
mat-dev-bounces@xxxxxxxxxxx [mailto:mat-dev-bounces@xxxxxxxxxxx] On Behalf Of Tsvetkov, Krum
Sent: Dienstag, 12. Januar 2010
16:03
To: Memory
Analyzer Dev list
Subject: [LIKELY JUNK][mat-dev]
Branching MAT 8.0 in SVN
Hi,
We expect that in the 1.0 release (we are targeting
beginning of April) we will add some APIs. It is also a good point in time to
reconsider our current APIs and adjust some of them if necessary.
Therefore I was thinking it will be good if we create a
branch for our current version – 8.0. This is the one included in Galileo and
slightly improved afterwards. We could use then the 8.0 as a more stable
release, and fix there only some important bugs if necessary.
We can then increase the version numbers in trunk to
something like 0.9 and make there the new development and necessary API
changes.
So my question is – do you
have any current activities / bugfixes for 8.0 which need to be finished before
splitting the code? What will be a good time for the split?
BTW, I have created a bugzilla entry to track the API
changes for 1.0: https://bugs.eclipse.org/bugs/show_bug.cgi?id=299371
Regards,
Krum
Tsvetkov
Pflichtangaben/Mandatory
Disclosure Statements: http://www.sap.com/company/legal/impressum.epx
Diese E-Mail kann
Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen
enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine
Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail
ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die
empfangene E-Mail. Vielen Dank.
This e-mail may contain trade secrets or
privileged, undisclosed, or otherwise confidential information. If you have
received this e-mail in error, you are hereby notified that any review,
copying, or distribution of it is strictly prohibited. Please inform us
immediately and destroy the original transmittal. Thank you for your
cooperation.