Release mails and update summary
"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? Thx T. [1] http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher [2] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-October/0859... [3] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-October/0859...
On 2013-10-23, at 10:54, "Torsten Bergmann" <astares@gmx.de> wrote:
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.
I don't think the updates is the right place, the right place is to attach proper links of the issues to the commit logs, because this is the only place you have a complete overview of what changed. We already have the link to the proper github branch for the updates files, but not for the updates themselves.
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?
Yes this is good plan, but we need to automatize the integration process further before. After the incident on last friday we see that there are still many parts of the integration (namely the issue closing) that get forgotten easily. But we have almost all the pieces, - a complete fogbugz api written in pharo - a complete issue checker written in pharo - automatic commit logs on github What is missing is, to - generate commit messages only from the issue numbers - automatically push a tag / close the issues when the integration process is complete Another problem, albeit solvable, is that the update.cs files are generated before actually exporting everything (or running the tests for that matter). That means we would have to modify the updates files afterwards on the server somehow and recommit them to the git repository containing the update files.
On 23 Oct 2013, at 10:54, Torsten Bergmann <astares@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
On Wed, Oct 23, 2013 at 10:54 AM, Torsten Bergmann <astares@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.
I agree! -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
participants (4)
-
Camillo Bruni -
Damien Cassou -
Marcus Denker -
Torsten Bergmann