Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-dev] When will be the project set for mylyn-e_3_3_m_2_x updated to Mylyn 2.2
Mik,

my preference would be to use a tag (version) like R_2_2_0_e_3_2 applied to all Mylyn plugins, even if there were no changes to them.
Then I can just select all mylyn eclipse.org plugins, and select Team/Switch to another Branch or Version and update to the version.

The project set is good way to start, but if you have projects/plugins already populated once, you have to remove them and then re-load them from the new project set. But if the tagging all plugins causes problem, re-loading project sets is workable solution and in the sense it is safer to use them, just in case new plugins are added or deleted from Mylyn project set.

So I would leave decision up to you. If you feel that project set is quite stable, solution 1 with version might work better.
If you feel there might be changes in the set of plugins from time to time, re-loading the project set might be safer solution, even if it takes longer to update the plugin set.

What do you think? Lubos

On Dec 20, 2007 9:44 AM, Mik Kersten <mik@xxxxxxxxxxx > wrote:

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

 

From: mylyn-dev-bounces@xxxxxxxxxxx [mailto:mylyn-dev-bounces@xxxxxxxxxxx] On Behalf Of Lubos and Alena Pochman
Sent: Wednesday, December 19, 2007 12:02 PM
To: mylyn-dev@xxxxxxxxxxx
Subject: [mylyn-dev] When will be the project set for mylyn-e_3_3_m_2_x updated to Mylyn 2.2

 

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

 


_______________________________________________
mylyn-dev mailing list
mylyn-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylyn-dev


Back to the top