Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Planning Meeting Notes - Discussion Topic

>  what to do when we are done?
>  c) do tag your released code with "annotated tag" (e.g. R4_2_0, R3_8_0)

This must only happen after Juno has been declared officially. We will discuss next week who adds these tags. For bundles that aren't split, we'll add both tags for better usability. The correct tags are 'R3_8' and 'R4_2'.

Dani

From: Curtis Windatt <Curtis_Windatt@xxxxxxxxxx>
To: eclipse-dev@xxxxxxxxxxx,
Date: 06.06.2012 16:15
Subject: [eclipse-dev] Planning Meeting Notes - Discussion Topic





Releng discussion topic:

 what to do when we are done?

  a) do not do anything :) in case we need emergency rebuild next week

  b) use care if you are using one of the "R4_HEAD" projects;  until we have renamed remaining R4_HEAD branches (approx. 6/27?)
       
Bug 378876 - change remaining 3 R4_HEAD repository branches to master

c) do tag your released code with "annotated tag" (e.g. R4_2_0, R3_8_0)



releng status:
 routine stuff to finish up:
 
381820 Add our docs to Juno Info Center
 
379493 Some 4.2. features and its feature branding plug-ins have lower version than in 3.8
 381814 update to final EMF build for Juno_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev



Back to the top