M5 - are we on track for major features implementations
API freeze
Transforms issues
Start levels
Minutes
Plan update
Everyone should send status on items on the Equinox plan to Tom.
UNC Path support
We didn't support UNC paths very well in 3.4
Significant effort is likely needed to address this, but there has been very little demand for it
Minimally should try to fail gracefully if we don't support it
Composite applications
Tom gave an overview of composite application framework progress
There was some brainstorming of how p2 would interact with a composite application hierarchy
API freeze
Little or no API work left to do for 3.5, so we are on track for API freeze
Transforms
Currently transforms are bundles, but considering making them framework extensions instead
We have problems on startup because the transform bundles are not starting early enough when using simpleconfigurator.
If the registry bundle starts before the transforms, then the transforms are not applied
Can workaround the problem by tweaking start levels
Start levels
Currently PDE build magically hard-codes start-levels and auto-start settings for various well-known bundles
There is now support in 3.5 for setting start levels and auto-start in the product file
The p2 publisher would need to duplicate the magic start level computation for well known bundles at metadata generation time
Would like to remove the "magic" from PDE build and consume start levels from the product files, but how do we set default values so that user's products don't break
One option is for PDE UI to copy start levels from the target platform into the product file when a bundle/feature is added to a product at development time
Likely still need compatibility mode for handling old product files that don't contain start level data
