Pharo 14: Start With a Separate Image and a Repeatable Project Trial
A new development environment is easier to evaluate when you can distinguish its own behavior from the behavior of your project. For Pharo 14, start with a separate trial environment, record what you selected, and use a small repeatable project test before deciding to move existing work.
What the October 26 release changes
The Pharo team announced version 14 on October 26, 2026. Its release notes highlight Mission Control, Pulse as a replacement for Spotter, reworked browsing and settings tools, refactoring infrastructure changes, and virtual-machine modernization. These changes provide several useful areas to explore; a release announcement alone does not establish that every external package or project works unchanged.
Pharo: version 14 release announcement
Understand what an image contains
Here, an image is a Pharo object space containing the runtime and development environment as well as objects loaded or created by its user. Launcher’s creation guide explains that a template archive includes an image and associated files such as sources and changes. Creating a fresh image and copying an existing project environment are therefore different starting points.
Pharo Launcher: image creation, templates and associated files
Keep a record of your working environment and its existing backup or recovery procedure before experimenting. Give the trial a distinct name and keep its outputs separate from important project data. A separate image helps organize the trial; it should not be treated as a security sandbox for arbitrary code or external operations.
Verify the selected version
The official download page recommends Launcher for obtaining core images and their appropriate virtual machines. However, parts of that page still name Pharo 12, and the image-creation guide contains a Pharo 8 example. Read these as historical examples. Check the actual template label and the running environment’s version rather than assuming a page’s generic stable label means Pharo 14.
Pharo: download routes and Launcher guidance
The Launcher repository documents creating images from templates, managing existing images, and finding or downloading the appropriate VM. Use the current official instructions for your platform. If your available template list does not identify the intended release, resolve that discrepancy before describing your trial as a Pharo 14 test; this article does not verify the live Launcher catalog or downloaded binaries.
Pharo Launcher: documented capabilities and VM selection
Try the tools before loading the whole project
Begin with a harmless demonstration: create a tiny example, browse and edit a method, run a test, and inspect a controlled failure. Then repeat the same actions with the tools you normally rely on. Record what became easier, what moved, and which operations need updated instructions for your team.
Next, load a small representative portion of your project using its documented loading process. Record the code revision, dependency versions and settings. Start with a disposable data set so that a trial failure does not become an accidental change to live information.
Write down a migration decision
- Confirm that the project loads and that its essential tests produce the expected results.
- Exercise one normal user workflow and one expected failure path; check the output, not just whether a window opens.
- If the project uses external libraries or services, test those boundaries explicitly with suitable test resources.
- Save and reopen the trial environment, then repeat the essential workflow.
- Keep unresolved differences with a reproduction and the exact image/VM details; check the relevant package’s support information before treating a mismatch as a core Pharo defect.
These are suggested acceptance checks, not results from an independently tested migration. A successful small trial supports expanding the test scope. A failed trial gives you a reproducible question to investigate while your working environment remains available. Decide to migrate on the evidence from your project, rather than on a release number alone.
