Skip to main content
Agenda
- M7 progress
- Bug 227675 Nested features should be hidden
- Feature patches, could multiple be installed on the same feature? were they capable of delivering partial jars?
Attendees
- Andrew Niefer
- Andrew Overholt
- Dave Stevenson
- DJ Houghton
- Jed Anderson
- John Arthorne
- Pascal Rapicault
- Scott Lewis
- Simon Kaegi
- Susan McCourt
- Tim Mok
Minutes
- PDE Build:
- Working on p2-enabled product builds
- Build will produce a p2 repository in addition to built product
- Installer
- Going to enable proxies in the installer
- Won't focus on further installer polish for 3.4
- Can focus more on making the installer first class in 3.4.1
- Associate and discovery sites
- Have a simple implementation released but it likely won't scale
- Working on splitting known repos from "discovered" repos
- Let user add discovered repos manually
- Plan to release trust authentication work and SSL support this work
- Update compatibility:
- platform.xml synchronization released
- Working on support for site policies
- May be some corner cases to test and resolve
- We now successfully parse and load all legacy update sites on EPIC
- Have not yet optimized case of legacy update site with pack200 enabled
- Solver:
- Tracking down bug in resolving configurations with optional bundles
- Patches
- Can currently support one patch per feature
- May need a special pre-processing step to merge multiple patches on a feature
- Nested features
- Currently we list all features in available software list, even when they don't appear in site.xml
- We'll look into putting features not listed in site.xml into another category
- We can then make this category hidden in the UI to provide an experience consistent with UM
Back to the top