On Wed, Jul 22, 2015 at 11:41 AM, Norbert Hartl <norbert@hartl.name> wrote:

> Am 22.07.2015 um 11:27 schrieb Sven Van Caekenberghe <sven@stfx.eu>:
>
> Nice.
>
> All this new stuff (decompiler, formatter), what's next (new changes log ? ;-).
>
That is a very good question. When will Epicea be integrated? The current stuff is broken anyway so less chance to worsen things :)

I hope we can integrate it soon. One of the points that delayed the integration is that we shouldn't have two overlapping mechanisms to log changes in the 5.0 release (traditional .changes/.sources file + Epicea). Then, I have made many small refactorings in Pharo 5.0 towards making the whole .changes thing removable. In particular, I tried to encapsulate reads/writes to the changes files, the uses of RemoteString, and others, into SourceFileArray (as a kind of fa��ade). A more clear and concentrated API in SourceFileArray is helping to understand how this thing works and how it could be removed and replaced. For example, SourceFileArray was a subclass of collection and there were many "SourceFiles at: 2" spread in the image to access the .changes file. Currently those are fixed but there is still some work to do. But I do believe we can have a removable .changes thing for Pharo 5 :-)

Mart��n