release-tools: get_bugs.pl and the --html switch
Hi, I just discovered a few issues in get_bugs.pl: 1. The two versions of release notes (txt and html) are always generated even without the --html switch 2. The same 'release_team_*' file is used in both versions, which means if you use --html, the html version of release_team is included in both versions of release notes (and without --html it's the text version that is included). I'm trying to fix those issues and I wonder if the --html switch is still needed. It's used only in a few places, and it's used in a wrong way: either the script think we are only generating html, or it is used in a test that is always true (if defined $html). Can we simply remove it ? -- Julian Maurice <julian.maurice@biblibre.com> BibLibre
I just discovered a few issues in get_bugs.pl:
I have an alternative script doing the same tasks. I don't know if I can / how I can push it on the release tools repo. It fixes few issues. Including the generation of the release team paragraph, which should be the same depending on current stable version, and not, as it is with get_bugs.pl, on the version released. I also generated note in Markdown, and then convert it from Markdown to HTML. Kind regards,
Le 12/02/2016 16:32, Frédéric Demians a écrit :
I just discovered a few issues in get_bugs.pl:
I have an alternative script doing the same tasks. I don't know if I can / how I can push it on the release tools repo.
It fixes few issues. Including the generation of the release team paragraph, which should be the same depending on current stable version, and not, as it is with get_bugs.pl, on the version released.
I also generated note in Markdown, and then convert it from Markdown to HTML.
Kind regards,
Please share it! :) I think you should be able to push to release-tools. -- Julian Maurice <julian.maurice@biblibre.com> BibLibre
Hi, On Fri, Feb 12, 2016 at 11:05 AM, Julian Maurice <julian.maurice@biblibre.com> wrote:
I think you should be able to push to release-tools.
I have now synced permissions in Gitolite so that all current RMs and RMaints have permission to push to the release tools repository (gitmaster@git.koha-community.org:release-tools). Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
I've pushed the release script I use on koha-release repo (thanks Galen). It doesn't touch at existing scripts. It just add a new one, that can be used, or not. The koha-release include this doc: NAME koha-release - Koha release tools SYNOPSYS koha-release v3.22.01..HEAD info koha-release v3.22.01..HEAD notes koha-release v3.22.01..HEAD html notes.html koha-release v3.22.01..HEAD pootle DESCRITPION The script "koha-release" generates release notes. It retrieves all bugs in Git for a commits range. For this reason, it must be launched from the root directory of a Koha Git repository. The bugs descriptions are retrieved from bugzilla using BZ REST API. It also generates contributors & signers & sponsor list (using Git informations), and translation percentage per language. The script works on a range of Git commits. This range generally has to cover commits from the last released version to the current one. For example, if the current version to be published is 3.22.3, and the previous one was tagged v3.22.02, this would be a valid range: v3.22.02..HEAD. The script is parametrized with a configuration file: "etc/config.yaml". See it for details. There is one Template Toolkit file used to generate the Markdown release notes file: "etc/notes.tt". Four commands: "koha range info" Outputs raw info in YAML format about the release. "koha range notes" Outputs the release notes in Markdown. "koha range html notes.html" Outputs the release notices in HTML by converting the Markdown version previously generated. "koha range pootle" Retrieves .po files from Koha Pootle Server, and write them in misc/translator/po directory. See "etc/config.yaml", section "pootle".
Awesome! 2016-02-12 14:55 GMT-03:00 Frédéric Demians <frederic@tamil.fr>:
I've pushed the release script I use on koha-release repo (thanks Galen). It doesn't touch at existing scripts. It just add a new one, that can be used, or not. The koha-release include this doc:
NAME koha-release - Koha release tools
SYNOPSYS koha-release v3.22.01..HEAD info koha-release v3.22.01..HEAD notes koha-release v3.22.01..HEAD html notes.html koha-release v3.22.01..HEAD pootle
DESCRITPION The script "koha-release" generates release notes. It retrieves all bugs in Git for a commits range. For this reason, it must be launched from the root directory of a Koha Git repository. The bugs descriptions are retrieved from bugzilla using BZ REST API. It also generates contributors & signers & sponsor list (using Git informations), and translation percentage per language.
The script works on a range of Git commits. This range generally has to cover commits from the last released version to the current one. For example, if the current version to be published is 3.22.3, and the previous one was tagged v3.22.02, this would be a valid range: v3.22.02..HEAD.
The script is parametrized with a configuration file: "etc/config.yaml". See it for details. There is one Template Toolkit file used to generate the Markdown release notes file: "etc/ notes.tt".
Four commands:
"koha range info" Outputs raw info in YAML format about the release.
"koha range notes" Outputs the release notes in Markdown.
"koha range html notes.html" Outputs the release notices in HTML by converting the Markdown version previously generated.
"koha range pootle" Retrieves .po files from Koha Pootle Server, and write them in misc/translator/po directory. See "etc/config.yaml", section "pootle". _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F
I didn't notice the mistake on the use of --html, because I ended using it everytime. When releasing either maintenance versions or major releases, you need the HTML version for the community site, and you want it calculated at the same time because you want them to be similar. For the release team file, that's another bug, and it can be fixed of course. 2016-02-12 12:32 GMT-03:00 Frédéric Demians <frederic@tamil.fr>:
I just discovered a few issues in get_bugs.pl:
I have an alternative script doing the same tasks. I don't know if I can / how I can push it on the release tools repo.
It fixes few issues. Including the generation of the release team paragraph, which should be the same depending on current stable version, and not, as it is with get_bugs.pl, on the version released.
I also generated note in Markdown, and then convert it from Markdown to HTML.
Kind regards, _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F
participants (4)
-
Frédéric Demians -
Galen Charlton -
Julian Maurice -
Tomas Cohen Arazi