Hello koha-devel, -first of all, BibLibre is still facing problem with mails on this list: it seems we can post, but don't recieve any mail from it. That's why I missed the "Upgrading Koha license" thread, (I say +1 for GPL 3 of course). So if you answer this mail, would you be kind to add me directly also. - The main reason of this mail are the release notes for Koha 3.10 : I made a lot of work to improve the script generating release notes, and I'm quite happy with the current result. I plan to release the text only notes, but also fancy and nice looking release notes (html & hopefully PDF, with a lot of details for enhancements, including some screenshots) What strikes me is that "Enhancements" mix patches that enhance an existing feature (and sometimes it's a tiny improvement), and patches that add a completely (and major) new feature. For readers I think it would be better to separate "Enhancements of an existing feature" and "New feature". What about adding separating "enhancements" in "enhancement" (of an existing feature) and "New feature" by adding the "new feature" to severity list ? The script generating release notes would be trivial to update to reflect that. Of course that would not be for 3.10, but 3.12+ cheers -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper
Paul, -first of all, BibLibre is still facing problem with mails on this list:
it seems we can post, but don't recieve any mail from it. That's why I missed the "Upgrading Koha license" thread, (I say +1 for GPL 3 of course). So if you answer this mail, would you be kind to add me directly also. -
The main reason of this mail are the release notes for Koha 3.10 : I made a lot of work to improve the script generating release notes, and I'm quite happy with the current result. I plan to release the text only notes, but also fancy and nice looking release notes (html & hopefully PDF, with a lot of details for enhancements, including some screenshots)
What strikes me is that "Enhancements" mix patches that enhance an existing feature (and sometimes it's a tiny improvement), and patches that add a completely (and major) new feature. For readers I think it would be better to separate "Enhancements of an existing feature" and "New feature".
What about adding separating "enhancements" in "enhancement" (of an existing feature) and "New feature" by adding the "new feature" to severity list ? The script generating release notes would be trivial to update to reflect that. Of course that would not be for 3.10, but 3.12+
+1 from me -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins@cpbibliography.com (web) http://www.cpbibliography.com/
Am 15.11.2012 17:49, schrieb Paul Poulain:
What about adding separating "enhancements" in "enhancement" (of an existing feature) and "New feature" by adding the "new feature" to severity list ? The script generating release notes would be trivial to update to reflect that. Of course that would not be for 3.10, but 3.12+
Good idea! +1 Marc Véron www.veron.ch
On Thu, Nov 15, 2012 at 11:49 AM, Paul Poulain <paul.poulain@biblibre.com>wrote:
What about adding separating "enhancements" in "enhancement" (of an existing feature) and "New feature" by adding the "new feature" to severity list ? The script generating release notes would be trivial to update to reflect that. Of course that would not be for 3.10, but 3.12+
+1 Kind Regards, Chris
Paul Poulain <paul.poulain@biblibre.com>
What about adding separating "enhancements" in "enhancement" (of an existing feature) and "New feature" by adding the "new feature" to severity list ?
OK, but I fear it makes it even more confusing for users that aren't also developers. Can they be next to each other and maybe "enhancement" "enhancement: new feature" to make it clear they're both the old enh? [order reversed to put most OT last]
-first of all, BibLibre is still facing problem with mails on this list: it seems we can post, but don't recieve any mail from it. That's why I missed the "Upgrading Koha license" thread, (I say +1 for GPL 3 of course). So if you answer this mail, would you be kind to add me directly also. -
Maybe the new lists.koha-community.org is confused about where is the Mail eXchange (MX) for biblibre.com? Check the mail.log or equivalent. It looks like it's hosted at dedibox who advertise Plesk - which is awful at handling domain name service (DNS) in my opinion - but maybe you're using a free software control panel like DTC and it's just slightly misconfigured. DNS can be awkward to fix because each change can take hours to spread everywhere (as some servers ignore your settings). Best wishes for a speedy recovery! ;-) -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and library systems developer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire (including development) at http://www.software.coop/
participants (5)
-
Chris Nighswonger -
Jared Camins-Esakov -
Marc Véron -
MJ Ray -
Paul Poulain