| <?xml version="1.0" encoding="utf-8"?> |
| <?xml-stylesheet type="text/xsl" href="../wtp.xsl"?> |
| <html> |
| <head> |
| <meta name="root" content="../../" /> |
| <title>web tools platform adopters</title> |
| </head> |
| <body> |
| <h1>WTP Adopters</h1> |
| |
| <h2>Introduction</h2> |
| <p> |
| WTP is a |
| <em>platform</em> |
| and so adoption by others is a major goal of the project. |
| You are a WTP |
| <em>adopter</em> |
| if you are a commercial vendor or an Open Source project |
| that is using or is planning to use WTP in one or more of |
| your products. This page lists information for WTP adopters. |
| </p> |
| <h3> |
| <a href="#hot-bugs">Hot Bugs</a> |
| </h3> |
| <h3> |
| <a href="#non-api-code-deprecation-policy"> |
| Non-API Code Deprecation Policy |
| </a> |
| </h3> |
| |
| <h2> |
| <a name="hot-bugs">Hot Bugs</a> |
| </h2> |
| <p> |
| The WTP project gives high priority to bugs that promote |
| adoption. If you are an adopter and need a fix for an |
| upcoming release, please follow the |
| <a href="hot_bug_process.html">hot bug process</a> to |
| request that your bug be placed on the Hot List. We can't |
| guarantee that we'll fix every Hot Bug, but we will give |
| them high priorties. |
| </p> |
| |
| <h3> |
| <h4> |
| <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=%5Bhotbug_request%5D&classification=WebTools&product=Web%20Tools&target_milestone=---&target_milestone=2.0&target_milestone=2.0%20M1&target_milestone=2.0%20M2&target_milestone=2.0%20M3&target_milestone=2.0%20M4&target_milestone=2.0%20M5&target_milestone=2.0%20M6&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&query_based_on=1.5.x%20Hot%20Bug%20Requests&field0-0-0=noop&type0-0-0=noop&value0-0-0=|,"> |
| WTP 2.0 Adopter Hot Bug Requests |
| </a> |
| </h4> |
| <h4> |
| <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=%5Bhotbug%5D&classification=WebTools&product=Web%20Tools&target_milestone=---&target_milestone=2.0&target_milestone=2.0%20M1&target_milestone=2.0%20M2&target_milestone=2.0%20M3&target_milestone=2.0%20M4&target_milestone=2.0%20M5&target_milestone=2.0%20M6&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&query_based_on=1.5.x%20Hot%20Bugs&field0-0-0=noop&type0-0-0=noop&value0-0-0=|,"> |
| WTP 2.0 Approved Hot Bugs |
| </a> |
| </h4> |
| </h3> |
| <h3> |
| <h4> |
| <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=%5Bhotbug_request%5D&classification=WebTools&product=Web%20Tools&target_milestone=---&target_milestone=1.5.1%20M151&target_milestone=1.5.2%20M152&target_milestone=1.5.3%20M153&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&field0-0-0=noop&type0-0-0=noop&value0-0-0=|,"> |
| WTP 1.5.3 Adopter Hot Bug Requests |
| </a> |
| </h4> |
| <h4> |
| <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=%5Bhotbug%5D&classification=WebTools&product=Web%20Tools&target_milestone=---&target_milestone=1.5.1%20M151&target_milestone=1.5.2%20M152&target_milestone=1.5.3%20M153&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&query_based_on=1.5.x%20Hot%20Bug%20Requests&field0-0-0=noop&type0-0-0=noop&value0-0-0=|,"> |
| WTP 1.5.3 Approved Hot Bugs |
| </a> |
| </h4> |
| </h3> |
| <h3> |
| <a href="../plans/1.5/adopter-hotlist-report.html"> |
| WTP 1.5 Adopter Hot Bug List |
| </a> |
| </h3> |
| <h3> |
| <a href="../plans/1.0.3/ramp-down-bugs-approval.html"> |
| WTP 1.0.3 Adopter Hot Bug List |
| </a> |
| </h3> |
| |
| <h2> |
| <a name="non-api-code-deprecation-policy"> |
| Non-API Code Deprecation Policy |
| </a> |
| </h2> |
| <h4>Status</h4> |
| <p> |
| The following policy is currently under discussion. We |
| expect to finalize it and implement it by mid-January. |
| </p> |
| <h4>Policy</h4> |
| <p> |
| WTP 1.0 does not include APIs for all functions that |
| adopters may require. Adopters therefore may elect to use |
| non-API code on the understanding that this code is subject |
| to change in future releases. Although we are not |
| technically obligated to preserve the non-API code in WTP |
| 1.5, we will make a best effort attempt to do so. We will |
| attempt to gracefully deprecate the non-API code for one or |
| two releases before completely removing it and forcing |
| adopters to migrate. |
| </p> |
| <p> |
| Since there is a lot of non-API code, we need to focus on |
| the portions of it that adopters are actually using. |
| Furthermore, we need to give the WTP development team tools |
| to determine if they are potentially breaking any adopter |
| product. Avoiding breakage in important, frequently used |
| non-API code will also be good practice for us in |
| preparation for evolving our API code in a non-breaking way. |
| </p> |
| <p> |
| We will therefore implement a deprecation policy for the |
| transition from WTP 1.0 to 1.5. Here are the main points: |
| </p> |
| <ol> |
| <li> |
| WTP will provide to adopters a simple build tool they |
| can use to scan their code and generate a report of |
| their usage of WTP code that can be provided to the WTP |
| development team, e.g. by attaching it to a Bugzilla |
| report. The reports will be purely statistical (usage |
| counts) and not reveal any details about the adopter's |
| code in order to preserve privacy. Adopters who |
| volunteerily opt in to this reporting process will |
| benefit from our efforts to reduce potential breakage in |
| their code as WTP evolves its code. |
| </li> |
| |
| <li> |
| WTP will provide to its developers a build tool that |
| scans our code and detects breakage in both API and |
| non-API code. Known API breakage will be considered a |
| "blocker" P1 bug. Breakage in non-API code will be |
| flagged if there is significant adopter usage of it, in |
| which case an effort will be made to preserve the |
| non-API code, or provide migration documentation. The |
| techniques used to evolve API code will be applied to |
| the important non-API code on a best efforts basis. In |
| cases where breakage is unavoidable, affected adopters |
| will be notified. |
| </li> |
| |
| <li> |
| When feasible, WTP will deprecate important non-API code |
| for a period of at least one major release. Adopters |
| will be encouraged to migrate to the new version between |
| releases. |
| </li> |
| |
| <li> |
| WTP will review the non-API usage reports for cases |
| where adopters are not using available API code and we |
| will inform adopters that API alternatives exist and |
| that they should migrate to them. WTP will not apply the |
| above deprecation policy to non-API code where API |
| alternatives exist. That is, adopters will be informed |
| of the API alternatives and given migration |
| instructions. Adopters will be required to migrate to |
| the WTP 1.0 API alternatives if we deem it necessarily |
| or advisable to remove the non-API code in WTP 1.5. |
| </li> |
| |
| <li> |
| WTP will review the non-API usage reports and use that |
| information to prioritise the evolution of non-API code |
| to API code. Non-API code that has high adopter usage |
| will be given the highest priority. |
| </li> |
| </ol> |
| |
| <h2>Tool to generate WTP usage report and determine non-API breakages</h2> |
| |
| <p> |
| Click <a href="scan4breakage.html">here</a> to learn how to scan for |
| adopter breakages as you develop code using Eclipse. |
| </p> |
| <p> |
| Click <a href="tool.html">here</a> to learn how to run the adopter breakage |
| tool in your build. |
| </p> |
| |
| <p> |
| Click <a href="extensionPtUsageScan.html">here</a> to learn how to run the |
| WTP extension point adopter usage scan for your product. |
| </p> |
| </body> |
| </html> |
