-Bug in the metadata generator for the fragments
- Add the check for consistency of 

- The picker should not need to know about the recommendation any more since the choice is done properly
- The objects returned of the dependency expander should have their constraints already updated such that recommendations awareness does not have to be pervasice
- We need to be able to get rid of recommendations
- We need to make sure that we don't report incompatibilities when required capabilities are not put to use
- the integration of recommendation is wacky
- recommendation for namespace is weird
- when we get a recommendation we don't check if it is compatible and if there could be a compatible one 
- how do we deal with multiple versions in the new dependencyExpander?

Need to do the operation name to put in the rollback DB
Write mini tests
Have the location of the former things be not hardcoded

Should we have a method like: be(InstallableUnit, Profile)?

Bug #5 Iterators, Collections and arrays
Our API and imeplementation is mishmach of arrays of installable units, iterators and collections, forcing us into silly / costly back and forth conversions.
- Iterators are good for their lazy aspect, however default iterators can't be resettable making it hard to pass them along for usage in other data structures.  We also don't know about their size.
- Arrays forces all the elements to be in memory at the time they are returned thus not scaling really well.
- Collections

- We need a generic downgrade capability
- The install / update / 
- 

Discussion topic:
- Is the rollback infrastructure core to the agent such that it can't be removed?
- What about the event model? Should we move to the event admin? Should the event be directly adaptable to something usefull? Is the event bus scalable? Who is posting there?
- Do a pass over all the API to make them more uniform?



The commit of the install registry does not happen in the same thread than the one where the event is sent.

Target content / PDE
Update configurator / update running when using PDE
Scenarios for metadata
UI Scenarios
Metadata for update
Add new phases (see SDD, deployment admin, UM hooks)
Infrastructure to the entry points
Infrastructure what has been installed from an entry point for rollback

Metadata generation, make sure that fragments are not being started


- update and remove should remember about the optional things that have been installed

- constraints
an overall file for a product / group
- gives the ability to broaden or restrict the constraints initially defined.
- it applies to all the IUs of 

---- 
Operations
Phases
Touchpoint actions

Patches construct
==========
With Jeff:
- constraint descriptors, they are special concepts from the director point of view
- installable unit doc
- rename of installable unit fragment into installable unit extensions
- metadata for update