View source for WTP Meeting Archive-Reference Page

==References from WTP Meetings==

This page is to hold some "old" references from previous WTP status meetings. 
Just to make finding them easier. 


:*[[WTP/Build/WTP Build Rhythm Schedule|WTP Build Rhythm Schedule]]

:*[[WTP Performance Tests]]

:*[http://build.eclipse.org/webtools/status/ WTP Build status page]

:*[[WTP UI Walkthroughs]]

:;*[http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_4.html Eclipse 3.4 Project Plan] for the [[Ganymede Simultaneous Release]].
:;*[[Eclipse/Galileo_Plan]]
:;*[[WTP Performance Tests]]
:;*[[WTP:_Tweaking_Access_Rules | Tweaking the Access Rules for WTP]]
:;*[[WTP How to: Branching Policy and Practices]]
:::In general, the minimum requirement is that if you branch a plug-in, you need to branch all the plug-ins in the corresponding map file. This is to make it easier for others to know what to load, to "be current" in a maintenance branch. It is fine to branch everything in a sub-project if you choose to, but still need to correspond to what's in a map file, and the map file should be updated to explain what it's used for. Map files can be re-organized some, if that helps make it easier to organize and understand what teams are working on what.
:::The names for branches should follow the pattern of 'R3_0_maintenance'. This will be the name for all 3.0.x maintenance work (not just the first, 3.0.1 maintenance work). Note that JSF and JPA code may use R2_0_maintenance, but their map files, will still be branched using R3_0_maintenance.
:*Instructions for tagging existing and new WTP wiki pages can be found at [[:Category:Eclipse Web Tools Platform Project | WTP's Category page]]; remember, we can create subcategories as well
:*This Week's Smoke Test Results
::[http://wiki.eclipse.org/WTP_Smoke_Test_Results_R30_102507 WTP Smoke Test Results R30]
:*Build Declaration Process Refined - See [[WTP Build Process and Procedures]]
:*Reminder:
::Information about process for milestone bugzilla line item planning has been added to the [[WTP_Bugs%2C_Workflow_and_Conventions | WTP Bugs, Workflow, and Conventions document]].
::PMC Candidate Review Request Checklist - See the updated [[WTP_PMC_Defect_Review | PMC Review]] document with attention to the "How To Prepare a PMC Defect Candidate" section
::[[New_Help_for_Old_Friends_II | Adopter Migration Information for WTP 2.0]] - Please add any details for your component.
:*Website
::Documentation on [[Web Tools Web Site Development Setup | Setting up your system for Web Tools Web site development]] and [[Using Web Tools Phoenix PHP templates]] is on the wiki at [[Web Tools Web Site Development]].
:*Bug Day
::Monitor and participate in [http://wiki.eclipse.org/BugDay Bug Day] if you would like.
::Mark any applicable bugs with keyword "bugday", but only if you'll have a representative on hand to respond through Bugzilla or in [[IRC]]
::[https://bugs.eclipse.org/bugs/report.cgi?x_axis_field=target_milestone&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= Current WTP Bug Day bugs] (~53)


:Project Meta data, for Project leads, especially, see "information about ..." from your subproject web page left nav bar.
::Go to [https://dev.eclipse.org/portal/myfoundation/portal/portal.php Foundation Portal]
::Login with committer ID
::Click on "[maintain] Project Info meta-data"

:Changes coming to IP Log management (more automated, but more for Project Leads to do?): See [[Development Resources/Automatic IP Log]]