[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipse-dev] Planning Meeting Notes - Dec 10, 2003
|
Platform UI
New look work continues
Problems view improvements released
General bug fixing and stability improvments
Mike Wilson/Ottawa/IBM@IBMCA
Sent by: eclipse-dev-admin@xxxxxxxxxxx
12/09/2003 03:36 PM
Please respond to eclipse-dev
To: eclipse-dev@xxxxxxxxxxx
cc:
Subject: [eclipse-dev] Planning Meeting Notes - Dec 10, 2003
-------------------
Discussion Topics
-------------------
Rel Eng:
- *proposed* 3.0 M6 build schedule
- Monday Dec 15 08:00 EST - 3.0 M6 Warm-up build
- this is just a warm up
- rebuilds will only be run if their are compile errors, missing
plugins
or the build is unusable. (Same as the integration build rebuild
policy)
- Tuesday, Dec 16 - 3.0 M6 Test Candidate build
- 3.0 M6 build toward Test candidate at 8 am, noon, 4 pm, and 8 pm
builds if map files are updated
- goal: a good build for the test pass on Wednesday
- all teams need to sign off on that candidate build is good enough
to
use for Wednesday's test pass
- for a rebuild, only team(s) requesting the rebuild need to recheck
and
sign off (although they may request other teams to revalidate
potentially affected functionality)
- we are writing a tool that will send an email to eclipse-dev the
names
of teams that have updated their map files for each build and thus
are
required to validate the build
- Wednesday, Dec 17 (all day) - 3.0 M6 Test pass
- intensive 1-day test pass on M6 candidate
- Thursday, Dec 18 - Builds toward Milestone candidate
- 3.0 M6 build toward Milestone candidate with 8 am, noon, 4 pm, and 8
pm
builds if map files are updated
- for a rebuild, only team(s) requesting the rebuild need to recheck
and
sign off (although they may request other teams to revalidate
potentially affected functionality)
- goal: a milestone candidate for Friday
- Friday, Dec 19
- final sanity check, all teams sign off, 3.0 M6 is released.
- Please note that these builds are run from cron. So if you don't have
your
submission in on time, you will have to wait for the next build bus :-)
----------
Outreach
----------
--------
Status
--------
Debug:
- bug fixing
- received/reviewed/integrated initial "source lookup facilities"
contribution. The initial contribution is a set of interfaces and
extension
points. Now awaiting contribution of implementation.
Ant:
- bug fixing
Rel Eng:
- writing tool to diff map files between milestone candidate builds to:
1) determine if there is new input requiring a rebuild
2) determine which teams have updated map file for build validation
- committed *work in progress* draft of build infrastructure/script
template
and documentation to org.eclipse.releng.basebuilder. Doc to be verified
by
Core (PDE Build), still working on instructions on automation of JUnit
plug-in testing, build publishing.
- bug fixing
Platform/JDT Text:
- bug fixing
- memory leak fixing
- improvements to the linked position infrastructure and navigation
- released reworked annotation handling to HEAD, highlight:
- prepares head less annotation handling
- separates annotation handling from markers
- explicitly introduces temporary annotations
- supports annotation types as subtypes of other annotation types
- supports sparse marker annotation type specifications
- simplifies handling of custom markers
JDT/UI:
- memory profiling
- bug fixing
- 2.1.3 bug fix (rename of package fragment)
Search:
- memory profiling
- bug fixing