[Pharo-dev] Release mails and update summary

Marcus Denker marcus.denker at inria.fr
Wed Oct 23 05:05:16 EDT 2013


On 23 Oct 2013, at 10:54, Torsten Bergmann <astares at gmx.de> wrote:

> "Pharo launcher" [1] has the ability to download and run images. It really 
> helps avoiding chaos on the hard disk and I can only recommend to others
> to give it a try.
> 
> One nice side effect is that one can download actual images depending
> on image number (update version). As we have seen this is also very 
> helpful when hunting bugs that are introduced by new updates, see [2]
> 
> Together with the release mails and its references to issues in the issue
> tracker one can easily reproduce each build. But one always has to look into the
> mail archive to get infos about the updates. 
> 
> Dont know how the release mails are written by integrators (manual or 
> automagically with a tool) but it looks like we switch to GitHub commit mails 
> these days [3].
> 
> IMHO it would also be helpful if we would have a single "Summary page" 
> on Pharo.org or directly under "updates.pharo.org" with a complete list 
> of all the updates:
> 
>   Pharo 3.0
>     - 30516
>     - 30515
>     - ...
>   Pharo 2.0 
>     - 20624
>     - 20623
>     - ...
> 
> and when clicking the update/version numbers one can get detailed infos about the update
> and the corresponding links to issue tracker. 
> Maybe the info is there in a format that can accessed also from within Pharo for future
> release management tools.
> 
> One possible way would be by having each FogBugz issue assigned an update number when 
> a fix get integrated and maybe such a summary page can be generated directly from the 
> issue tracker. Is this already existing or planned?
> 
> Any comments?
> 

do it. The problem is that not everything that would be nice can be done just because the day
has just 24 hours.

	Marcus





More information about the Pharo-dev mailing list