Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[tm-dev] TM 3.2.2 is released - Policy for 3.2.2+

TM Committers,

 

The TM 3.2.2 release has been made available along with Helios SR2.

Thank you all for your contributions!

 

Moving forward, we are starting to accept backport patches into 3.2.2+. Here’s the policy (unchanged from past years and Streams):

-          Each fix MUST exist in the HEAD stream (3.3)

-          There MUST be a separate bug item identifying the backport, assigned a “3.2.2+” target milestone

-          There MUST be a patch attached to that bug, with one committer giving a Review+

-          The committer must not only commit the fix but is also responsible for releasing into the Mapfile

o   See http://wiki.eclipse.org/TM/Code_Streams for correct branches, tag syntax and team project set files

-          Our Legacy Builder polls the Mapfile once a day and runs a Build when the Mapfile changed.

o   3.2.2+ builds appear as M20110301-1130 or similar on the download page.

 

One note regarding plugin and feature version updates.

 

In the past, we would have required updating the bundle and feature versions for 3.2.2+ fixes, i.e. plugin and feature versions would need to go 3.2.3.qualifier. That’s always been quite some effort and I’m unsure about the value. What do others think, should we update the bundle and feature versions or live with just qualifier updates which the builder performs (mostly) automatically?

 

The only drawback that I can think of is that adopters will find it a little bit harder to see what bundles/features are from 3.2.2+ versus which ones are from 3.2.2.

 

Any thoughts / comments ?

 

Thanks,

Martin

--

Martin Oberhuber, SMTS / Product Architect – Development Tools, Wind River

direct +43.662.457915.85  fax +43.662.457915.6

 


Back to the top