We tag the releases once they are ready, and the build system checks
out using those tags. So you could either check out the project set after
the release is done, or check out the specific tag. I just documented the
format that we use at:
http://wiki.eclipse.org/Mylyn_Contributor_Reference#Checkout
Each release is tagged with
<code>R_</code>. For example, Mylyn 2.2.0 for Eclipse 3.4 is
tagged as <code>R_2_2_0</code> and the branched Eclipse 3.3
plug-ins are tagged <code>R_2_2_0_e_3_2</code>.
My question is, would you prefer if we tagged everything
as R_2_2_0_e_3_2, not just the changed plug-ins? This could have
implications for the build system so we’ll have to check with Rob on the
policy for t hat.
Mik
From: Lubos and Alena
Pochman [mailto:pochmans@xxxxxxxxx]
Sent: Thursday, December 20, 2007 8:17 AM
To: mik@xxxxxxxxxxx; Mylyn developer discussions
Subject: Re: [mylyn-dev] When will be the project set for
mylyn-e_3_3_m_2_x updated to Mylyn 2.2
Thanks Mik,
no I do not have any trouble. I just wanted to make sure that I get the final
version of Mylyn 2.2.
So I assume mylyn-e_3_3_m_2_x points always to 2.x development and it is
updated on regular bases.
And if I want to get Mylyn 2.2 final I download the project set when Mylyn 2.2
gets released (tomorrow).
Is this correct or should I use other method (SVN tags, or updating to HEAD
tomorrow) to get Mylyn 2.2 code?
Thanks, Lubos
On Dec 20, 2007 9:03 AM, Mik Kersten <mik@xxxxxxxxxxx> wrote:
Hi Lubos,
It should always be up-to-date,
since we add branched plug-ins to it as we go. We did the port of the
branched plug-ins yesterday. Are you having any trouble with the project
set?
Mik
Guys,
when will be the project set for mylyn-e_3_3_m_2_x updated to Mylyn 2.2?
Lubos
_______________________________________________
mylyn-dev mailing list
mylyn-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylyn-dev