WTP 2019-04-25

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 <<

Next Meeting: May 16, 2019 (3 weeks)

WTP Calendar

WTP Calendar Sync this calendar along with your Google account

For overall SimRel dates, see the Simultaneous Release Calendar

Main Agenda Items

WTP 3.14 for Eclipse IDE 2019-06

• IPluginDescriptor breakages were all fixed in time for M1. Thank you!

• For bugs that should be in the PLAN, use the "plan" keyword and a 3.14 or 3.14 milestone or release candidate target.

• A request was opened for a Java 12 Facet. John Collier has agreed to make the same changes as we've had for recent Java releases for at least the next few.

• Make sure you add a 3.14 release, scheduled for June 19, 2019, to your subproject under https://projects.eclipse.org/projects/webtools . With the Bugzilla information filled out in your individual project metadata, you can see overviews like https://projects.eclipse.org/projects/webtools/releases/3.10.0/bugs . When you login in and then Edit from the PMI page, the link to create a New Release is on the right.

• There are mentions of issues with installing and using the Glassfish Tools release on 2019-03. Awaiting a response from Danny Ju about the status of the project and if these are real bugs.

Themes for WTP 3.14

• Moving to EPL 2.0 (P2, but some will slip to 3.14M1)
  • EPL FAQ section on relicensing
  • Webtools branch of Nitin's clone has some changes that can help with updating file headers, even if files have been renamed or moved in the git history. Be sure to check the "Copyright tool" preference page once it's built and installed! It can be built using Maven or via exporting as a deployable plug-in from within Eclipse. A built snapshot can be downloaded and added to your dropins folder for use.
    • Check your repository histories for move/rename comments and update the Copyright Tool Git preference page's exclusions
    • Check the main Copyright Tool preference page for the default text to be inserted into unlicensed source files--it is still EPL v1.0 upstream.
    • Run the tool, check the changes (this will be affected by disk I/O speed, so use the fastest one you can). It should be writing the same output to the Console view as well as copyrightLog.txt in the workspace directory.
    • Take heed of anything in the Console output under "Retains a reference to an outdated license, EPL v1.0". Those were strings referencing EPL v1's URL, but not in the copyright comment.
      • With a lot of files to check for the Source Editing repo, I had to find a way to review them faster than through the Git Staging view. That ended up being the git cli. git diff within the local clone will show changes in a scrollable text UI. As with the less command, you can use the / key to enter a Regular Expression search string: ^diff (the beginning of line followed by "diff" followed by a space), which is how each file's changes begin. After pressing Enter/Return, tapping n will jump to the next regex match (meaning the next file), while N will jump to the previous one. This allowed me to flip through the largely identical changes pretty quickly, looking for incorrect indentations or other problems (e.g. "t" used instead of "*" in the copyright comment) as if they were breaking a pattern, much like a few random frames spliced into a film reel will stick out. These outliers I then corrected from within Eclipse, and in the case of test reference files that didn't have a notice on them to start with, often undid the changes to avoid tampering with the tests (ours often rely on specific character offsets in those files).
    • Update/replace the about.htmls (license notices) that refer to EPL v1.0, ideally with text from late November, 2017 or newer. Source Editing's wst/jst schemas plug-ins contained more than just EPL notices because of the third party content, so be sure you look through those carefully.
    • Recommended: adopt the shared license feature, version 2.0.0.qualifer, and you can remove the license key and text value from your feature.properties file. The build will use the license key from the license feature when it writes out the P2 metadata, so while you still need to refer to it in your feature.xml, you don't need to carry a copy of it in your feature project. Some features in WTP are already using the shared license feature, some are not, let's get it to 100%.

Moving to EPL 2.0 : Status

Project	Status	Comments
Common		Nitin did this one
Java EE		Nick's initial attempt caused test failures
JSF		Nick did it - https://bugs.eclipse.org/543811
Dali		https://bugs.eclipse.org/543812
Server		Complete
Web Services, WSDL
JSDT & Node.js tools		Nitin's attempt did not pass all tests, might have a conflict now 3.14M1
Source Editing		See the whole section above
Release Engineering

LSP4E Exploration

On hold pending resources (time). JavaScript EPP package for 2019-06 expected to be based on Wild Web Developer.

• Bugs at a glance
• SimRel FAQ and Plan
• Bugzilla naming: Put the simrel into the Version that's reported against, e.g. "3.12 (2018-12)" since that's filled in by reporters, but keep the Target Milestone simple as before (3.13, 3.13 M1, etc.) so that bug queries don't get too complicated for developers.

• 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

• We will meet once per Milestone / RC scheduled for 1 week before the candidate build day. Declare is 5 days later with the corresponding EPP 2 days after that, and official SimRel/IDE availability one day after that.
  • Dev meeting on 4/4, M1 candidate built on April 11, M1 declare on April 16
  • Dev meeting on 4/25, M2 candidate built on May 2, M2 declare on May 7
  • Dev meeting on 5/16, M3 candidate built on May 23, M3 declare on May 28
  • Dev meeting on 5/23, RC1 candidate built on May 30, RC1 declare on June 4
  • Dev meeting on 6/6, RC2 candidate built on June 6 if changes are PMC approved, to be declared on June 11
  • Release: June 19, 2019

3.13 Schedule

April 4	M1 status meeting
April 11	M1 build candidate
April 16	WTP M1 declared
April 18	M1 EPP approved
April 19	2019-06 M1
April 25	M2 status meeting
May 2	M2 build candidate
May 7	WTP M2 declared
May 9	M2 EPP approved
May 10	2019-06 M2
May 16	M3 status meeting
May 23	M3 build candidate
May 23	RC1 status meeting
May 28	WTP M3 declared
May 30	M3 EPP approved
May 30	RC1 build candidate, changes should have project lead review and approval
May 31	2019-06 M3
June 4	WTP RC1 declared
June 6	Release status meeting
June 6	RC1 EPP approved
June 6	RC2 build candidate if needed, changes require PMC + 1
June 7	2019-06 RC1
March 12	WTP RC2 declared
June 13	RC2 EPP approved
June 14	2019-06 RC2
June 19	3.14 quiet release
June 19	2019-06 GA

3.14 Builds

• Release and CI builds will continue to use Java 8.
• Latest CI builds: https://hudson.eclipse.org/webtools/view/webtools_CI/
• Smoke Test - coming soon!
• Bug opened for the repeated Dali build test failures
• Bugs reported since our last meeting

Bug and Feature Highlights

Blockers, Hot-Bugs, Hot-Features

• Blocker and Critical
• Hotbugs
• Hotfeatures
• Hotfeatures - triaged with helpwanted

Focus On Quality

JSF and Java EE builds are currently broken.

• Compiler Warnings Per Project (click link at left, then scroll down for the warnings table)
• 2019-03-06: 148,307 (3 high severity)
• 2019-02-14: 148,311 (4)
• 2018-11-09: 148,353 (25)
• 2018-09-26: 148,372 (23)
• 2018-08-16: 148,353 (4)
• 2018-07-05: 148,272

Other business - Long term tracking items

• Automated Error report logging - Now in JavaEE EPP
• The WTP Forum, https://www.eclipse.org/forums/eclipse.webtools (Subscribe for emails)
  • ServerTools Forum, https://www.eclipse.org/forums/index.php/f/88/
  • JavaServer Faces Forum, https://www.eclipse.org/forums/index.php/f/148/
  • WTP Incubator Forum, https://www.eclipse.org/forums/index.php/f/114/
  • We need more WTP participation (triaging / fixing / coordinating / watching)
• Dashboard
• Incident reports
• JST Problems Query

Reference

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 Who's Who

• WTP Git Usage/Discussion page

• New Help for Old Friends

• WTP Smoke Test Scenarios, Smoke Test Template, WTP Smoke Test Results

• Provisional API

• Luna release retrospective

• Standard Format Plans

• how/when to branch code?

• IP Logs selector