[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[wtp-pmc] WTP PMC telecon agenda for Tuesday, July 11th 2006
|
Call info:
- Tollfree in the US:
866-214-3176
- Alternate: 404-827-9098
- Access code: 8870689#
Call Time: 7am PDT / 10am PDT
This is a long agenda, so we may end up postponing some
topics until next week.
Agenda:
- Community review [Lawrence]
- Callisto/1.5 release feedback?
- Screencam demo download
numbers – see [3].
- Podcast with EZ on WTP and
Callisto
- EclipseCon 2007 program
kickoff (see attached email and slide deck)
- 1.5/Callisto Debrief
- Any open issues? Bad bugs?
- Process issues and scheduling
[Tim]
- AI [Tim]: “full”
release review slidedeck (no progress last week; on vacation)
- Update on inactive committer
and record review (Tim, Lawrence)
- UI test infrastructure
donation offer from Instantiations
- STP integration –
process and communication
- Sybase visual JSF/JJSP
designer contribution update
- Status
- Placement w.r.t. projects and
graduation timing concerns
- Bjorn’s statement on
Eclipse policy w.r.t. committer “bootstrapping” – see
[2].
- Requirements and 2.0 Planning
(Jochen)
- 1.5.1 Status (David)
- 1.0.3 Rampdown status and open
issues [David]
- See rampdown schedule in David’s
email (attached)
- 8 open defects still targeted
to 1.0.3 [1]
- JSF [Gerry[
- Tech preview debrief/feedback
- Planning process for next
release
- Dates
- Incorporating feedback from
internal review
- Integration of feature lists
and plans with WTP mechanisms
- Other planning
issues/concerns?
- Graduation review planning
- Dali/JPA [Neil]
- Tech preview debrief/feedback
- Planning process for next
release
- Dates
- Facets, APT, and other
architectural mods (incorporating feedback from internal review)
- Integration of feature lists
and plans with WTP mechanisms
- Build integration
- Other planning
issues/concerns?
- Graduation review planning
- ATF [Robert]
- Community building plan and
awareness issues (EMO concerns)
- Planning process for initial
release (tech preview)
- Dates
- Integration of feature lists
and plans with WTP mechanisms
- Build integration
- Other planning
issues/concerns?
[1] https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=Web+Tools&target_milestone=1.0.3+M103&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=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=
[2] [From Bjorn] At the discretion of the PMC,
new components can get the "free pass for committers" scheme.
I'm sorry that it's confusing, but here's the logic: you have to vote in new
committers to join an existing group of committers, but if you are forming a
new group, you (optionally) get a free pass. So because your significant new
code contribution would be forming a new group, you get the free pass status.
[3] [From Wayne Beaton] As
of Sunday evening, there have been 10,804 downloads of the install-eclipse
screencam demo and 4,538 of the install-wtp screencam demo.
I'm not sure if there is any
significance. Perhaps this is an indication that around 42% of relative
newcomers are curious about webtools...
|
From: eclipse.org-pmc-leads-bounces@xxxxxxxxxxx on behalf of Richard
Gronback [richard.gronback@xxxxxxxxxxx]
Sent: Friday, July 07, 2006 12:45 AM
To: eclipse.org-pmc-leads@xxxxxxxxxxx
Cc: Ian Skerrett
Subject: [eclipse.org-pmc-leads] EclipseCon 2007 Program Committee
Attachments: EclipseCon for Plenary June 2006.ppt; ATT2220758.txt
Hello All,
In case you haven't heard, a new approach will be used for next year's EclipseCon to determine the tracks and their content. PMCs and working groups will recruit and select presentations in their respective areas of expertise. The first thing we'll need to do is determine the members of this committee, so if each PMC can nominate a representative, I can narrow the mailing list accordingly.
Please see the attached slides for more info if you missed the plenary session at the last council meeting. Slide 7 includes a set of starter allocations, which we need to discuss and refine. Do you feel you should have more or less of each, are there missing tracks, unnecessary tracks, etc.?
Finally, if you have good ideas for next year's 3 keynote topics/speakers, please let me know.
Thanks for your help,
Rich
--
Richard C. Gronback
Borland Software Corporation
richard.gronback@xxxxxxxxxxx
+1 860 227 9215
Attachment:
EclipseCon for Plenary June 2006.ppt
Description: EclipseCon for Plenary June 2006.ppt
From: wtp-dev-bounces@xxxxxxxxxxx on behalf of David M Williams
[david_williams@xxxxxxxxxx]
Sent: Monday, July 10, 2006 2:33
PM
To: wtp-dev@xxxxxxxxxxx
Subject: [wtp-dev] Thanks for 1.5
... ready to start again?
Attachments:
ATT2720373.txt
Much thanks and
congratulations for our "Callisto release" on 6/30. Now after such a long break :) is everyone ready to
begin the rhythm again? I suggest we
focus on 1.5.1 and 1.0.3 for a bit, before focusing on declaring 2.0
(I know, all teams may be different, but
.. timing is already tight for most of us). I suggest we smoke test 1.5.1 this week, and produce our final 1.0.3
build next week. (and, I'm assuming,
we'll have weekly 1.5.1 M-builds declared the rest of this month).
Detailed schedule below .. let me
know if anyone sees any holes, or has other comments. 1.5.1 Wed.
7/12 (end of day) - code done and released for this week's 1.5.1 M build.
Thur. 7/13 - smoke test (rebuild only if
blocking or critical regression found) Friday 7/14 - noon (eastern): Weekly 1.5.1 M-build declared
[every week, we'll following this wed., thur.,
fri pattern, where no code should be casually released after end of day wednesday]. 1.0.3 due 7/28 http://www.eclipse.org/webtools/development/pmc_call_notes/2006-06-13.html
7/17 final code for 1.0.3 7/18 smoke test 1.0.3 7/19 1.03 RC declared 7/20 -
begin week-long-no-changes phase, adopter can/should do acceptance
testing 7/26 - prepare update site/zips,
etc. 7/28 - official 1.0.3
release 2.0 TBD