| [tm-dev] TM 3.3.x maintenance builds |
|
TM Committers, As our TM 3.3 release is complete, I have resumed builds towards TM 3.3.1. Please review
http://www.eclipse.org/tm/development/relnotes/3.3/tm-news-3.3.html if there’s anything else to mention about 3.3. Like in previous years, for now we’ll use the TM HEAD Stream for 3.3.1 maintenance work. We can branch off as soon as we need to (eg to make API additions for 3.4), but for now the plan is to keep in HEAD until 3.3.1 (Sep 24) and branch then. By convention, every checkin for 3.3.1 should have an associated bugzilla for tracking, see
http://wiki.eclipse.org/TM/3.3_Ramp_down_Plan I will care for tagging the Mapfile (approx. once a week) and updating version numbers; Let me know if there’s an urgent need for tagging earlier. If you tag/release yourself please use a “R33x_v201106291510” format, see also
http://wiki.eclipse.org/TM/Code_Streams On the downloads page, maintenance builds show up as “N-builds” or “I-builds”. The p2 update site for automated I-builds is
http://download.eclipse.org/tm/signedUpdates Occasionally I will promote a build to
http://download.eclipse.org/tm/updates/3.3milestones Let me know if there’s any questions. Thanks, Martin -- Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River direct +43.662.457915.85 fax +43.662.457915.6 |