:The help has a file called "Limitations and Known Issues" - this functions as a type of readme so that users can easily search for problems that have known workarounds. I wouldn't mind taking 2 minutes to discuss:

+

:a) whether or not we want to keep this in the help or move it to a wiki where we can update it as workarounds are found

+

:b) or if we keep it in the help, to remind everyone that they need to review the current content and add anything they can think of.

+

+

*Minutes:

+

: Keep with using help doc, not on wiki

+

: Kate: opened a bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=233531 233531], please use to add updates using comments

:228366: been in many releases, not a regression, looking at it very hard, might wait till 301, opened a bug to platform but that's only a part of the problem, change it to RC3 and see if its possible. Gary: BE is mainframes, LE is windows

+

: David:frequency of occurence if its only on mainframes

+

:233196: Lary: suspect shouldn't be blocking

+

:231257: Phil: just got it today, will not be fixed for this release, main bug on platform is targeted to 3.5, leave to major, retargted to match the platform bug

+

: 231348: Chuck: haven't seen it, but haven't been able to reproduce it

+

+

=== Thursday to Tuesday HEAD Builds? ===

+

+

See [http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg06109.html Proposal] to keep HEAD very clean, so it's essentially an I-build without 'release'.

+

+

Do they need to be automated? 6 hours? 8 hours? Or, is "on demand" easy enough?

== Release Review Requirements ==

== Release Review Requirements ==

Line 249:

Line 261:

Had good discussion of what the JavaDoc issues are, with promises to follow up on wtp-releng.

Had good discussion of what the JavaDoc issues are, with promises to follow up on wtp-releng.

+

David: 15 min videos to cover the project, suggest to a couple made for WTP bybproject leads

+

+

:Demo:

+

:Raghu/JSF: yes 10 mins

+

:Neil/JPA: yes 15 mins

+

:Kaloyan/EJB/JEE5capabilities: yes, a few mins, not a full movie

+

:Nitin: JSDT, will take a look and see what's new

+

:Phil/Brad: yes

+

:Kathy: a few things, enhancements or new functionalities?

+

:David: Major enhancements are find also

+

:Chuck: yah some things that we can show, a few wizard that Kaloyan has contributed

WTP Development Status Meeting 2008-05-08

Attendees

Announcements And Reports

Focus on Requirements Planning (David today ... and Raghu)

Nearly Done. Two requests of Project Leads:

Let's triage remaining list of 'plan' keyword items that are not resolved, and not marked future or not targeted. (i.e. it doesn't make sense to have marked 'plan' but untargeted ... or, what does it mean?)

Issues

The help has a file called "Limitations and Known Issues" - this functions as a type of readme so that users can easily search for problems that have known workarounds. I wouldn't mind taking 2 minutes to discuss:

a) whether or not we want to keep this in the help or move it to a wiki where we can update it as workarounds are found

b) or if we keep it in the help, to remind everyone that they need to review the current content and add anything they can think of.

228366: been in many releases, not a regression, looking at it very hard, might wait till 301, opened a bug to platform but that's only a part of the problem, change it to RC3 and see if its possible. Gary: BE is mainframes, LE is windows

David:frequency of occurence if its only on mainframes

233196: Lary: suspect shouldn't be blocking

231257: Phil: just got it today, will not be fixed for this release, main bug on platform is targeted to 3.5, leave to major, retargted to match the platform bug

231348: Chuck: haven't seen it, but haven't been able to reproduce it

Thursday to Tuesday HEAD Builds?

See Proposal to keep HEAD very clean, so it's essentially an I-build without 'release'.

Do they need to be automated? 6 hours? 8 hours? Or, is "on demand" easy enough?

Release Review Requirements

Need zip file of about.html files by 5/15

Release Review will be June 4th, 11 AM Eastern Time. All (sub) project leads are encouraged to phone in.

IP Log

In general, Project leads should review our IP Log for completeness and correctness.

non-Committer Contributions

* bugzillas with contributed patches should be marked with contributed keyword

* There are some WTP IP Tools to help explore potential contributions.

Copyrights

Make sure copyrights are up-to-date and according to Eclipse Foundation form:

In general, the minimum is if you branch a plug-in to branch all the plug-ins in the corresponding map file. It is fine to branch everything if you choose as well. We may need to reorganize map files slightly and we can investigate that on a case by case basis. This is intended to be a living document and open to evolutions and improvements.

Instructions for tagging existing and new WTP wiki pages can be found at WTP's Category page; remember, we can create subcategories as well

Upcoming Focus Item

Past Focus Items

Invalid - Enhancement does not fit with the scope of the project or is already implemented.

helpwanted keyword - This is a valid request, but due to committer resources and other priorities, outside help will be needed to make this happen.

Future - I would use this in conjunction with the helpwanted keyword. I use this for legitimate requests that are important but will not make any planned release, but likely will make a future release.