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

Difference between revisions of "WTP 2018-06-21"

(Project links)
(WTP 3.11: Eclipse SimRel 2018.09)
 
(17 intermediate revisions by 3 users not shown)
Line 13: Line 13:
 
* Subscribe to updates for your Gerrit repositories! Check https://git.eclipse.org/r/#/settings/projects .
 
* Subscribe to updates for your Gerrit repositories! Check https://git.eclipse.org/r/#/settings/projects .
 
* [wtp-pmc] [https://bugs.eclipse.org/bugs/show_bug.cgi?id=534819 Java EE Configuration Editors Project to be terminated] -  https://dev.eclipse.org/mhonarc/lists/wtp-pmc/msg02445.html
 
* [wtp-pmc] [https://bugs.eclipse.org/bugs/show_bug.cgi?id=534819 Java EE Configuration Editors Project to be terminated] -  https://dev.eclipse.org/mhonarc/lists/wtp-pmc/msg02445.html
 +
* Vote for Nitin Dahyabhai to join the WTP PMC and to take over as PMC lead has concluded successfully. Congratulations, Nitin!
  
 
=== WTP Calendar  ===
 
=== WTP Calendar  ===
Line 25: Line 26:
  
 
<br>
 
<br>
 +
Next meeting: July 5, 2018.
  
 
== Main Agenda Items ==
 
== Main Agenda Items ==
Line 34: Line 36:
  
 
* Tag Repositories for the release
 
* Tag Repositories for the release
** Releng repos, too
+
** Releng repos, too [Nick: On what date should this be done?]
** Suggested tag name: R3_10 or R3_10_0, project lead's choice (see below)
+
** Suggested tag name: R3_10 or R3_10_0, project lead's choice (see below) [Nick: Could we move to 3.10 tag and 3.10.x branch, so these values align with BZ versions?]
** R3_10_maintenance branches may be created, although we expect not to use them (see below)
+
** R3_10_maintenance branches may be created, although we expect not to use them (see below) [Nick: Could we use 3.10.x?]
  
 
* New and Noteworthy
 
* New and Noteworthy
Line 45: Line 47:
 
* Releng Lead Nick does not have commit rights to Web Services and Source Editing. Project leads can log into the [https://dev.eclipse.org/portal/myfoundation/portal/portal.php Portal], select the [view] link for your project, and nominate him after making sure you can find at least 2 other people to vote, or the election will fail. :D
 
* Releng Lead Nick does not have commit rights to Web Services and Source Editing. Project leads can log into the [https://dev.eclipse.org/portal/myfoundation/portal/portal.php Portal], select the [view] link for your project, and nominate him after making sure you can find at least 2 other people to vote, or the election will fail. :D
  
* [BLOCKER] Eclipse blocks while doing coding actions - https://bugs.eclipse.org/bugs/show_bug.cgi?id=487598 - https://git.eclipse.org/r/#/c/123376/ - PR provided but no one reviewed/merged for o.e.w.common.modulecore.
+
* [BLOCKER, 3.11] Eclipse blocks while doing coding actions - https://bugs.eclipse.org/bugs/show_bug.cgi?id=487598 - https://git.eclipse.org/r/#/c/123376/ - PR provided but no one reviewed/merged for o.e.w.common.modulecore.
  
 
== WTP 3.10: Photon ==
 
== WTP 3.10: Photon ==
Line 51: Line 53:
 
* Release pages will be streamlined more in keeping with [https://www.eclipse.org/webtools/releases/3.9.5/ 3.9.5's].
 
* Release pages will be streamlined more in keeping with [https://www.eclipse.org/webtools/releases/3.9.5/ 3.9.5's].
 
** New and Noteworthy will be worked into the release page itself, although we might reconsider creating pages per-milestone.
 
** New and Noteworthy will be worked into the release page itself, although we might reconsider creating pages per-milestone.
 +
* It is time to triage any open [https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=bug_status&y_axis_field=product&z_axis_field=&no_redirect=1&query_format=report-table&classification=WebTools&target_milestone=3.10&target_milestone=3.10+%28Photon%29&target_milestone=3.10+M1&target_milestone=3.10+M2&target_milestone=3.10+M3&target_milestone=3.10+M4&target_milestone=3.10+M5&target_milestone=3.10+M6&target_milestone=3.10+M7&target_milestone=3.10+RC1&target_milestone=3.10+RC2&target_milestone=3.10+RC3&target_milestone=3.10+RC4&target_milestone=3.10.0&target_milestone=3.10.0+M1&target_milestone=3.10.0+M2&target_milestone=3.10.0+M3&target_milestone=3.10.0+M4&target_milestone=3.10.0+M5&target_milestone=3.10.0+M6&target_milestone=3.10.0+M7&target_milestone=3.10.0+RC1&target_milestone=3.10.0+RC2&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap bugs still targeted for 3.10] to a future release like 3.11.
  
 
=== 3.10 Schedule ===
 
=== 3.10 Schedule ===
Line 63: Line 66:
  
 
* [https://wiki.eclipse.org/Photon/Simultaneous_Release_Plan#Schedule Photon Schedule]
 
* [https://wiki.eclipse.org/Photon/Simultaneous_Release_Plan#Schedule Photon Schedule]
 
=== 3.10 Builds ===
 
 
* [[WTP_Smoke_Test_Results| Smoke Test]]
 
 
=== WTP 3.10.0: Releng ===
 
 
==== In Progress ====
 
 
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=534583 534583 - update download page template to link to parent pom for dependency information]
 
 
  
 
== WTP 3.11: Eclipse SimRel 2018.09 ==
 
== WTP 3.11: Eclipse SimRel 2018.09 ==
Line 83: Line 75:
 
*** Should we establish an unchanging milestones site URL?
 
*** Should we establish an unchanging milestones site URL?
 
** It's incumbent on projects to test and make sure their contributions to the simrel repository work.
 
** It's incumbent on projects to test and make sure their contributions to the simrel repository work.
 
+
** Shortened release intervals and fewer RCs mean higher scrutiny on late changes
 +
* Bugzilla naming suggestion: Put the simrel into the '''Version''' that's reported against, keep the '''Target Milestone''' simple as before (3.11, 3.11 M1, etc.) so that bug queries don't get too complicated.
  
 
Tentative schedule is for 13 weeks, 4 cycles per year:
 
Tentative schedule is for 13 weeks, 4 cycles per year:
Line 91: Line 84:
 
* one week RC2
 
* one week RC2
 
* one week quiet and release
 
* one week quiet and release
** doesn't mesh well with fortnightly meetings, suggestions?
 
 
** [Nick] suggest we do one meeting every 3 weeks (one per sprint / milestone) scheduled for 1 week before the +0 release day.  
 
** [Nick] suggest we do one meeting every 3 weeks (one per sprint / milestone) scheduled for 1 week before the +0 release day.  
 
:** M1 candidate on 7/13, devel meeting on 7/05
 
:** M1 candidate on 7/13, devel meeting on 7/05
Line 128: Line 120:
 
|-
 
|-
 
| 8/31
 
| 8/31
| RC1 build candidate
+
| RC1 build candidate, all changes need project lead approval
 
|-
 
|-
 
| 9/04
 
| 9/04
Line 137: Line 129:
 
|-
 
|-
 
| 9/07
 
| 9/07
| RC2 build candidate
+
| RC2 build candidate, all changes need PMC +1 approval
 
|-
 
|-
 
| 9/11
 
| 9/11
Line 157: Line 149:
  
 
=== 3.11 Releng ===
 
=== 3.11 Releng ===
==== (Not) In Progress ====
+
 
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=534057 534057 - JavaEE - org.eclipse.jst.j2ee.tests tests disabled because failing]
+
==== TODO ====  
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=534553 534553 - JavaEE - JEM tests not yet enabled]
+
 
 +
After Photon is live:
 +
 
 +
* Tag projects for 3.10; create maintenance branches
 +
 
 +
* Update wtp.releng.* projects for 3.11 builds; set new baseline in parent pom
 +
 
 +
* Rename jobs from _R310 suffix to _master since we probably won't need to do maintenance builds for 3.10.x with a new milestone every 3 weeks and a new .Final every quarter.
 +
 
 
==== In Progress ====
 
==== In Progress ====
  
 
* New download pages - https://bugs.eclipse.org/bugs/show_bug.cgi?id=534583
 
* New download pages - https://bugs.eclipse.org/bugs/show_bug.cgi?id=534583
  
* Build guide - https://bugs.eclipse.org/bugs/show_bug.cgi?id=489026 - update http://git.eclipse.org/c/webtools/webtools.releng.aggregator.git/tree/README.adoc with latest info
 
  
 
==== Done ====
 
==== Done ====
 +
 +
* Build guide - https://bugs.eclipse.org/bugs/show_bug.cgi?id=489026 - update http://git.eclipse.org/c/webtools/webtools.releng.aggregator.git/tree/README.adoc with latest info
 +
 +
==== (Not) In Progress ====
 +
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=534057 534057 - JavaEE - org.eclipse.jst.j2ee.tests tests disabled because failing]
 +
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=534553 534553 - JavaEE - JEM tests not yet enabled]
  
 
== Bug and Feature Highlights ==
 
== Bug and Feature Highlights ==
Line 247: Line 252:
 
{{WTPProjectTable|servertools||235 unit tests, 421 integration|green}}
 
{{WTPProjectTable|servertools||235 unit tests, 421 integration|green}}
 
{{WTPProjectTable|jsdt||1467 (3 skip)|green}}
 
{{WTPProjectTable|jsdt||1467 (3 skip)|green}}
{{WTPProjectTable|sourceediting||10,891|green}}
+
{{WTPProjectTable|sourceediting||10,891 (2 skip)|green}}
{{WTPProjectTable|javaee|jeetools|585 (was 1,448)|green}}
+
{{WTPProjectTable|javaee|jeetools|585 (2 skip) (was 1,448 total)|green}}
{{WTPProjectTable|dali||4,705 (2 skip)|green}}
+
{{WTPProjectTable|dali||4,705|green}}
 
{{WTPProjectTable|jsf||675|green}}
 
{{WTPProjectTable|jsf||675|green}}
{{WTPProjectTable|webservices||664|green}}
+
{{WTPProjectTable|webservices||570 (was 664)|green}}
  
 
==== More Links ====  
 
==== More Links ====  

Latest revision as of 01:56, 22 June 2018

WTP Development Status Meeting

Remember, any committer can add an agenda item. Typically, short announcements or news items go in the "Announcements" section at the beginning. Longer items or issues requiring discussion should go in the "Other business" section at end.


To join the call:

>> https://eclipse.zoom.us/j/6300031838 <<


Announcements And Special Reports

WTP Calendar

WTP Calendar Sync this calendar to your mobile device



For overall Photon dates, see the Simultaneous Release Calendar


Next meeting: July 5, 2018.

Main Agenda Items

  • New_Help_for_Old_Friends_X migration guide needs some updates from:
    • wsdl2j update? (Keith)
    • BREE changes in Source Editing (Nitin), taking longer with complications from the repository re-org, expected Saturday
    • others?
  • Tag Repositories for the release
    • Releng repos, too [Nick: On what date should this be done?]
    • Suggested tag name: R3_10 or R3_10_0, project lead's choice (see below) [Nick: Could we move to 3.10 tag and 3.10.x branch, so these values align with BZ versions?]
    • R3_10_maintenance branches may be created, although we expect not to use them (see below) [Nick: Could we use 3.10.x?]
  • New and Noteworthy
    • Send Nitin screenshots and verbage for 3.10's new features. JAX-RS 2.1, advanced source lookup, and Java EE API JavaDoc should be advertised!
  • Releng Lead Nick does not have commit rights to Web Services and Source Editing. Project leads can log into the Portal, select the [view] link for your project, and nominate him after making sure you can find at least 2 other people to vote, or the election will fail. :D

WTP 3.10: Photon

  • Release pages will be streamlined more in keeping with 3.9.5's.
    • New and Noteworthy will be worked into the release page itself, although we might reconsider creating pages per-milestone.
  • It is time to triage any open bugs still targeted for 3.10 to a future release like 3.11.

3.10 Schedule

6/11 3.10 RC4 build RC4 build
6/15 Photon RC4
6/27 3.10 and Photon GA

Reminder 1: PMC approvals are needed for bugfixes in RCx releases.

Reminder 2: If applicable, please add a section to the New Help for Old Friends page.

WTP 3.11: Eclipse SimRel 2018.09

  • We're going to 11!
  • After a year of quarterly service releases that allowed for API additions, the Planning Council is switching the simultaneous release to quarterly "minor" releases, and WTP is going with them, barring any reasoned objections. FAQ
    • API additions can happen in each release
    • API deprecation to removal timeframe will remain 2 calendar years
    • The "simrel" update site URL will remain the same going foward
      • Should we establish an unchanging milestones site URL?
    • It's incumbent on projects to test and make sure their contributions to the simrel repository work.
    • Shortened release intervals and fewer RCs mean higher scrutiny on late changes
  • Bugzilla naming suggestion: Put the simrel into the Version that's reported against, keep the Target Milestone simple as before (3.11, 3.11 M1, etc.) so that bug queries don't get too complicated.

Tentative schedule is for 13 weeks, 4 cycles per year:

  • one week decompress and plan
  • (3) three week milestones
  • one week RC1
  • one week RC2
  • one week quiet and release
    • [Nick] suggest we do one meeting every 3 weeks (one per sprint / milestone) scheduled for 1 week before the +0 release day.
    • M1 candidate on 7/13, devel meeting on 7/05
    • M2 candidate on 8/03, devel meeting on 7/26
    • M3 candidate on 8/24, devel meeting on 8/16
    • RC candidate on 9/14, devel meeting on 9/06

3.11 Schedule

7/13 M1 build candidate
7/17 M1 declare
7/20 SimRel 2018.09 M1
8/03 M2 build candidate
8/07 M2 declare
8/10 SimRel 2018.09 M2
8/24 M3 build candidate
8/28 M3 declare
8/31 SimRel 2018.09 M3
8/31 RC1 build candidate, all changes need project lead approval
9/04 RC1 declare
9/07 SimRel 2018.09 RC1
9/07 RC2 build candidate, all changes need PMC +1 approval
9/11 RC2 declare
9/14 SimRel 2018.09 RC2
9/18 3.11 quiet release
9/19 SimRel 2018.09 GA

3.11 Builds

3.11 Releng

TODO

After Photon is live:

  • Tag projects for 3.10; create maintenance branches
  • Update wtp.releng.* projects for 3.11 builds; set new baseline in parent pom
  • Rename jobs from _R310 suffix to _master since we probably won't need to do maintenance builds for 3.10.x with a new milestone every 3 weeks and a new .Final every quarter.

In Progress


Done

(Not) In Progress

Bug and Feature Highlights

Focus on Quality

Blockers, Hot-Bugs, Hot-Features

Project status section

  • Each project may choose to post information about:
    • What have you been working on?
    • What are you working on for our next meeting?

Other business - Long term tracking items


Reference

Release Process & Releng Stuff

Category Links
Repos &

Gerrit requests

Tests Results &

Compilation Warnings

Release Docs
Policy Docs
  1. Hotbug Policy
  2. Hotfeature Policy

Project links

Project Status Browse Git p2 Repo Tests Pending Changes Gerrit Builds Clone
common green git gitiles lastSuccessfulBuild 232 tests gerrit master git clone ssh://${GITUSER}@git.eclipse.org:29418/webtools-common/webtools.common.git
Project Status Browse Git p2 Repo Tests Pending Changes Gerrit Builds Clone
servertools green git gitiles lastSuccessfulBuild 235 unit tests, 421 integration tests gerrit master git clone ssh://${GITUSER}@git.eclipse.org:29418/servertools/webtools.servertools.git
Project Status Browse Git p2 Repo Tests Pending Changes Gerrit Builds Clone
jsdt green git gitiles lastSuccessfulBuild 1467 (3 skip) tests gerrit master git clone ssh://${GITUSER}@git.eclipse.org:29418/jsdt/webtools.jsdt.git
Project Status Browse Git p2 Repo Tests Pending Changes Gerrit Builds Clone
sourceediting green git gitiles lastSuccessfulBuild 10,891 (2 skip) tests gerrit master git clone ssh://${GITUSER}@git.eclipse.org:29418/sourceediting/webtools.sourceediting.git
Project Status Browse Git p2 Repo Tests Pending Changes Gerrit Builds Clone
javaee green git gitiles lastSuccessfulBuild 585 (2 skip) (was 1,448 total) tests gerrit master git clone ssh://${GITUSER}@git.eclipse.org:29418/jeetools/webtools.javaee.git
Project Status Browse Git p2 Repo Tests Pending Changes Gerrit Builds Clone
dali green git gitiles lastSuccessfulBuild 4,705 tests gerrit master git clone ssh://${GITUSER}@git.eclipse.org:29418/dali/webtools.dali.git
Project Status Browse Git p2 Repo Tests Pending Changes Gerrit Builds Clone
jsf green git gitiles lastSuccessfulBuild 675 tests gerrit master git clone ssh://${GITUSER}@git.eclipse.org:29418/jsf/webtools.jsf.git
Project Status Browse Git p2 Repo Tests Pending Changes Gerrit Builds Clone
webservices green git gitiles lastSuccessfulBuild 570 (was 664) tests gerrit master git clone ssh://${GITUSER}@git.eclipse.org:29418/webservices/webtools.webservices.git


More Links


WTP Meeting Archive-Reference Page

Back to the top