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.