M4 or Beta 2?
The intent of this message is to clarify the relationship between the M4 milestone and Beta 2. The Jazz team will deliver the M4 milestone this weekend. We consider the M4 milestone
as a release candidate for Beta 2 and will improve M4 until it is promoted to Beta 2. Beta 2 will be available in mid December.
Everyone is welcome to use M4 and provide feedback but since Beta 2 is coming very soon after M4 you will likely want to skip M4 and wait for Beta 2.
as a release candidate for Beta 2 and will improve M4 until it is promoted to Beta 2. Beta 2 will be available in mid December.
Everyone is welcome to use M4 and provide feedback but since Beta 2 is coming very soon after M4 you will likely want to skip M4 and wait for Beta 2.
4 answers
berliner wrote:
https://jazz.net/development/DevelopmentItem.jsp?href=content/project/plans/jazz-plan-0.6.html
here is the relevant section:
The format of data in the Jazz repository is expected to change
significantly throughout the Platform 0.6 release cycle. Starting with
Platform 0.6 M1 (aka Beta 1), we will provide tools for exporting
critical data from one milestone's repository and importing it into the
next milestone's repository; e.g., from M1 to M2, from M2 to M3, and so
on. We will also provide tools for migrating directly from one Beta to
the next Beta (or to the final release); e.g., from Beta 1 to Beta 2,
from Beta 2 to Beta 3, and Beta 3 to the 0.6 release. So while there is
no guarantee of smooth sailing and 100% compatibility, there will always
be a documented way to make headway.
Will there be a migration path from Beta 1 to Beta 2? or M2(a) to Beta
2?
yes, this is actually spelled out in our release plan.
https://jazz.net/development/DevelopmentItem.jsp?href=content/project/plans/jazz-plan-0.6.html
here is the relevant section:
The format of data in the Jazz repository is expected to change
significantly throughout the Platform 0.6 release cycle. Starting with
Platform 0.6 M1 (aka Beta 1), we will provide tools for exporting
critical data from one milestone's repository and importing it into the
next milestone's repository; e.g., from M1 to M2, from M2 to M3, and so
on. We will also provide tools for migrating directly from one Beta to
the next Beta (or to the final release); e.g., from Beta 1 to Beta 2,
from Beta 2 to Beta 3, and Beta 3 to the 0.6 release. So while there is
no guarantee of smooth sailing and 100% compatibility, there will always
be a documented way to make headway.