Re: [linuxtools-dev] Attention: Major changes for Tycho 0.13 compatibility
* akurtakov [2011-10-06 02:28]: > >> 3. Bundle/Feature naming - that's what provoked this mail, I appreciate the > >> fact that tycho devs showed the problem. It's confusing (at least) > >> especially > >> in feature.xml files (include vs. import). My suggestion is to make the > >> feature > >> have the module name (e.g. org.eclipse.linuxtools.changelog) and if there > >> is a > >> module with the same name rename it to smth that describes it better e.g. > >> org.eclipse.linuxtools.changelog.core. Changelog is used intentionally > >> because > >> it's already this way. > > > > +1 for clean core/UI separation and clearer bundle names. Note that > > bundle re-names will affect consumers just like you mentioned earlier, > > Alex, so we should be _very_ careful about such changes. > > There is no better time to do such thing. Post 1.0 is gonna be too much > problem. Agreed, we standardize and define this well ahead of 1.0 (Juno/June 2012). Andrew ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] Eclipse Build: Designating a stable branch eclipse37
On 10/05/2011 09:49 AM, akurtakov wrote: Shouldn't we build later milestone? Yup, I'll tackle M2 soon. This work will be reused for 3.7.1, at least the git fetch part. Sounds good. We can use the eclipse37 branch for that and cherry pick everything that is needed over. If all or most of the commits are need we can create an eclipse371 branch from master HEAD. ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] Eclipse Build: Designating a stable branch eclipse37
On 18:23:55 Thursday 06 October 2011 sami wagiaalla wrote: > On 10/05/2011 09:49 AM, akurtakov wrote: > > Shouldn't we build later milestone? > > Yup, I'll tackle M2 soon. > > > This work will be reused for 3.7.1, > > at least the git fetch part. > > Sounds good. We can use the eclipse37 branch for that and cherry pick > everything that is needed over. If all or most of the commits are need > we can create an eclipse371 branch from master HEAD. The problem is that 3.7.1 is not tagged properly as can be read on platform releng list. Even Kim is waiting for component leads to tag it themself. I hoped that M2 is in better shape and use it for 3.7.1 once it's tagged. Alex > ___ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/linuxtools-dev ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
[linuxtools-dev] Indigo SR1 vs 0.8.1 Release
This is just to inform everybody that Indigo SR1 and the 0.8.1 release I put out are not matched (they should have been). The SR1 release was built on 08/30 while the 0.8.1 release was built on 09/26. The 0.8.1 release build differs from Indigo SR1 in that it contains a fix for missing Lttng experiment dialog messages. The SHA-1 for Indigo SR1 is f920f76d4d254b51878bc6d0838a6b02d5d38c22 while for 0.8.1 it is b5d263782a2d384025a07cfd136fefc0fad7218e. -- Jeff J. ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
