Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Search results

Page title matches

Page text matches

  • === Non compliant projects for Indigo release ... status/plans? === ...l requirements". They are simply EDP/IP requirements and must be done, for release.
    5 KB (598 words) - 14:15, 15 June 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    10 KB (1,459 words) - 10:59, 30 June 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    13 KB (1,834 words) - 15:05, 31 January 2013
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    11 KB (1,595 words) - 14:11, 14 July 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    12 KB (1,789 words) - 14:07, 21 July 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    13 KB (1,844 words) - 14:12, 28 July 2011
  • On the topic of "Can new things show up in Sim. Release Service Releases?" ... we have previously agreed "yes". Any discussion? ...new content must still meet all the other requirements of the Simultaneous Release, such as signed, externalized strings, etc. In fact, the "requirement" that
    7 KB (1,008 words) - 13:42, 3 August 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    13 KB (1,863 words) - 14:43, 4 August 2011
  • ...main project needed from that repository. The instructions and process for Juno (SR1 and SR2) are very similar to those for Kepler (SR0, in June 2013) exce ...of this writing) and input for update releases will be in a branch named '<Release>_maintenance' (so, for example, Neon_maintenance is for Neon.1, Neon.2 and
    24 KB (3,873 words) - 05:06, 9 October 2020
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    13 KB (1,824 words) - 13:53, 11 August 2011
  • ...to cross-project list. (How to handle "individual projects" vs. those that release as a "group", e.g. WTP?, Platform?) ...little excuse after that, not to have announced and be planning next years release).
    10 KB (1,533 words) - 13:25, 2 October 2013
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    13 KB (1,846 words) - 13:59, 18 August 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    12 KB (1,733 words) - 11:20, 10 April 2012
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    11 KB (1,542 words) - 16:30, 25 August 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    11 KB (1,599 words) - 13:39, 8 September 2011
  • ...l be in RC4. This leaves us with very little time to do any testing on the release (Of course we've tested this on internal builds but the RCs where not testa ...R1. In other, cases, if had been found too late, shortly after the Service Release, it would have been impossible to "back out" the change, and would have onl
    10 KB (1,658 words) - 17:54, 7 September 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    12 KB (1,727 words) - 15:16, 8 September 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    11 KB (1,541 words) - 13:59, 15 September 2011
  • ...ument is for primarily for developers of the June 2014 Luna [[Simultaneous Release]]. ...or Luna] (which typically becomes available around April or May before the release). -->
    13 KB (1,871 words) - 11:26, 29 July 2014
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    11 KB (1,667 words) - 10:46, 27 September 2011
  • ...'''MWE 2.3 Release Review''', as part of the upcoming '''Juno Simultaneous Release'''. ===New in this release===
    3 KB (396 words) - 02:56, 8 June 2012
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    12 KB (1,737 words) - 13:54, 29 September 2011
  • == Juno Plan and Requirements == ...n| Planning Document]] with SR dates ... I consider the document "done for Juno" ... except for links (and content) for requirements and tracking. (That is
    8 KB (1,186 words) - 14:31, 6 October 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    12 KB (1,761 words) - 14:06, 6 October 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    13 KB (1,906 words) - 14:03, 13 October 2011
  • ...4.0, of the UML2 project, to be released as part of the Juno simultaneous release of Eclipse. The source code for this new version of the project is managed ...instead of CVS as its source code management system for the upcoming Juno release. In fact, all of the changes for UML2 4.0 have been committed (and pushed)
    39 KB (5,556 words) - 22:11, 20 February 2014
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    15 KB (2,261 words) - 13:21, 27 October 2011
  • == Juno Plan and Requirements == ..., and can not say for sure we would use them in the aggregation builds for Juno, so not sure it should be "required" this year ... but, it would go a long
    11 KB (1,697 words) - 11:26, 16 November 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    13 KB (1,954 words) - 16:05, 28 October 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    13 KB (1,917 words) - 13:57, 3 November 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    13 KB (1,809 words) - 15:36, 10 November 2011
  • == Juno Plan and Requirements == ...s_Release_Requirements#Changes_for_Juno_Release| proposed changes for Juno Release]].
    12 KB (1,800 words) - 02:42, 7 December 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    12 KB (1,746 words) - 15:01, 17 November 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    12 KB (1,725 words) - 15:12, 1 December 2011
  • Congrats on Juno!! Hope you had (or having) some good time off. ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar]
    8 KB (1,206 words) - 12:06, 19 July 2012
  • == Subversive ramp down plan for Juno == For reference, see the [[Juno/Simultaneous Release Plan]],
    4 KB (567 words) - 03:59, 3 February 2013
  • == Juno Plan and Requirements == ...ne for handsome [http://eclipse.org/projects/releases/releases.php?release=juno "participating projects"] page.
    7 KB (1,016 words) - 13:47, 7 December 2011
  • == Juno == ...nts. Changes or clarifications needed? Or, approve "as is", unchanged from Juno?
    7 KB (998 words) - 14:16, 7 November 2012
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    12 KB (1,713 words) - 14:49, 8 December 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    12 KB (1,746 words) - 14:59, 15 December 2011
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    12 KB (1,729 words) - 16:00, 5 January 2012
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    9 KB (1,320 words) - 13:52, 14 June 2012
  • ...with the absolute final build being RC4: final aggregation build 2/15, for release on 2/24. == Juno ==
    7 KB (1,051 words) - 13:51, 4 January 2012
  • * Juno SR1 Announced - Thanks! ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar]
    12 KB (1,706 words) - 10:56, 4 October 2012
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    13 KB (1,828 words) - 15:08, 12 January 2012
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    13 KB (1,824 words) - 14:59, 19 January 2012
  • This plan is about the detailed timing and planning of the last release candidates for Target Management 3.4 ([http://www.eclipse.org/tm/developmen For reference, see the [[Juno/Simultaneous Release Plan]],
    7 KB (1,099 words) - 14:47, 15 January 2013
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    12 KB (1,795 words) - 15:05, 2 February 2012
  • ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar] ...t to a specific release or "future" if planning to fix but not in the next release
    11 KB (1,568 words) - 15:05, 8 March 2012
  • * Juno M5 declared - Thanks everyone. ...7469ddj9tjlk%40group.calendar.google.com&ctz=America/New_York Simultaneous Release Calendar]
    12 KB (1,805 words) - 14:54, 9 February 2012

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)

Back to the top