9. Bootstrap
• Create an image from a git repository
• Control what the image contains
• Easier to make changes
• Enforces Modularity
10. Boostrap
• Working for Pharo3 as a prototype
!
• Can we even use this for Pharo4 on the build
server?
11. One File Pharo
• .sources, .changes. .image
!
• It is time to simplify that!
12. Epicea
• Replace .changes
• High level model:
• aggregate changes (refactoring)
• serialized to disk independent of source model
14. Step2: Sources
• It is 2014: Memory is cheap.
• Complexity is expensive
• Why not just put the sources in the image?
• Just current version (compressed, of course)
• Code history is in Monticello (or Git)
15. Slots
• First class Instance Variables
• Already in Pharo3, but compatible (ivar Slot)
• For Pharo4: Provide different Slot kinds