← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
| Time | Nick | Message |
|---|---|---|
| 00:32 | khall joined #koha | |
| 00:55 | inlibro joined #koha | |
| 00:58 | dpk_ joined #koha | |
| 01:04 | alexbuckley joined #koha | |
| 01:55 | inlibro joined #koha | |
| 02:01 | koha-jenkins | Project Koha_20.11_D10 build #17: UNSTABLE in 5 hr 12 min: https://jenkins.koha-community[…]oha_20.11_D10/17/ |
| 02:03 | Project Koha_20.11_U20 build #3: SUCCESS in 48 min: https://jenkins.koha-community[…]Koha_20.11_U20/3/ | |
| 02:10 | Project Koha_20.11_D9 build #5: SUCCESS in 55 min: https://jenkins.koha-community[…]/Koha_20.11_D9/5/ | |
| 02:10 | Yippee, build fixed! | |
| 02:10 | wahanui | Congratulations! |
| 02:10 | koha-jenkins | Project Koha_20.11_D10 build #18: FIXED in 54 min: https://jenkins.koha-community[…]oha_20.11_D10/18/ |
| 02:11 | Project Koha_20.11_D11 build #7: SUCCESS in 57 min: https://jenkins.koha-community[…]Koha_20.11_D11/7/ | |
| 02:55 | inlibro joined #koha | |
| 03:55 | inlibro joined #koha | |
| 04:08 | koha-jenkins | Project Koha_19.05_D9 build #340: SUCCESS in 45 min: https://jenkins.koha-community[…]oha_19.05_D9/340/ |
| 04:10 | Project Koha_20.05_D10 build #141: SUCCESS in 48 min: https://jenkins.koha-community[…]ha_20.05_D10/141/ | |
| 04:11 | Project Koha_20.11_D11 build #8: SUCCESS in 46 min: https://jenkins.koha-community[…]Koha_20.11_D11/8/ | |
| 04:13 | Project Koha_19.11_D10 build #103: UNSTABLE in 51 min: https://jenkins.koha-community[…]ha_19.11_D10/103/ | |
| 04:22 | Project Koha_20.11_D10 build #19: SUCCESS in 1 hr 0 min: https://jenkins.koha-community[…]oha_20.11_D10/19/ | |
| 04:56 | inlibro joined #koha | |
| 05:08 | Oak joined #koha | |
| 05:25 | mtj | hey #koha |
| 05:26 | ..i was about to push the new 20.11 packages, but just realised that bug 26741 was not added | |
| 05:26 | huginn | Bug http://bugs.koha-community.org[…]_bug.cgi?id=26741 minor, P5 - low, ---, dcook, Signed Off , Make rabbitmq-server suggested rather than required |
| 05:27 | dcook | mtj: I've been wondering about that... |
| 05:27 | Question for Joubu I guess? | |
| 05:27 | mtj | yeah, ill email him |
| 05:32 | i added a new rmq section to the install guide, in anticipation | |
| 05:33 | https://wiki.koha-community.or[…]#Install_RabbitMQ | |
| 05:38 | josef_moravec joined #koha | |
| 05:54 | mtj | i cc'd you in the email dcook :) |
| 05:54 | dcook | cheers, mtj |
| 05:56 | inlibro joined #koha | |
| 06:07 | chriss joined #koha | |
| 06:21 | cait joined #koha | |
| 06:35 | koha-jenkins | Project Koha_20.05_D10 build #142: ABORTED in 2 hr 20 min: https://jenkins.koha-community[…]ha_20.05_D10/142/ |
| 06:56 | inlibro joined #koha | |
| 07:10 | fridolin joined #koha | |
| 07:23 | lds joined #koha | |
| 07:24 | lds | hi |
| 07:24 | wahanui | privet, lds |
| 07:25 | cait joined #koha | |
| 07:26 | cait1 joined #koha | |
| 07:28 | fridolin | hi there |
| 07:31 | reiveune joined #koha | |
| 07:31 | reiveune | hello |
| 07:33 | did joined #koha | |
| 07:54 | magnuse | \o/ |
| 07:55 | alex_a joined #koha | |
| 07:55 | alex_a | Bonjour |
| 07:55 | wahanui | hello, alex_a |
| 07:56 | fridolin | bravo for 20.11 first release |
| 07:56 | inlibro joined #koha | |
| 07:56 | * fridolin | warming up for RMaint ;) |
| 07:59 | * cait1 | sends cookies for fuel |
| 08:18 | paul_p joined #koha | |
| 08:20 | kohaputti joined #koha | |
| 08:45 | ashimema | morning Koha |
| 08:52 | mtj | hi peeps |
| 08:52 | ashimema | hi mtj |
| 08:53 | cait1 | good morning |
| 08:53 | mtj | hiya, i think we bump 26741 till 20.11.01 |
| 08:54 | koha-jenkins | Project Koha_20.05_D10 build #143: FAILURE in 4 min 12 sec: https://jenkins.koha-community[…]ha_20.05_D10/143/ |
| 08:56 | inlibro joined #koha | |
| 09:07 | kohaputti joined #koha | |
| 09:10 | nlegrand joined #koha | |
| 09:10 | nlegrand | hello #koha |
| 09:14 | magnuse | bonjour nlegrand |
| 09:17 | nlegrand | Salut magnuse! |
| 09:26 | TimothyAlexis joined #koha | |
| 09:27 | TimothyAlexis | bugs 27050 and 27080 are ready for sign off |
| 09:27 | bug 27050 | |
| 09:27 | huginn | Bug http://bugs.koha-community.org[…]_bug.cgi?id=27050 enhancement, P5 - low, ---, timothy_alexis.vass, Needs Signoff , Allow multiple category_codes in delete_patrons.pl |
| 09:27 | TimothyAlexis | bug 27080 |
| 09:27 | huginn | Bug http://bugs.koha-community.org[…]_bug.cgi?id=27080 enhancement, P5 - low, ---, timothy_alexis.vass, Needs Signoff , Add --statute-barred option to cleanup_database.pl to purge all fees where the item has been returned and the fee is older than the given number of days. |
| 09:31 | cait1 | Joubu: will try to catch rangi for the bugzilla clean-up - i stole some other tasks, hope that was ok :) |
| 09:32 | Joubu | yes sure, thanks! |
| 09:39 | cait1 | @later tell caroline can you give me a heads up when the manual is branched? and 21.05 manuals are available? I will add them to the website then |
| 09:39 | huginn | cait1: The operation succeeded. |
| 09:44 | davidnind joined #koha | |
| 09:56 | inlibro joined #koha | |
| 10:02 | kohaputti joined #koha | |
| 10:10 | alex_a joined #koha | |
| 10:18 | huginn | News from kohagit: Correct Ubuntu versions in release notes <https://git.koha-community.org[…]282d24bad9a36c4d3> |
| 10:18 | News from kohagit: Koha 20.12 - start of a new dev cycle <https://git.koha-community.org[…]6b0a09be0d29880b5> | |
| 10:18 | News from kohagit: v20.11.00 <https://git.koha-community.org[…]30743dc22c1cd6443> | |
| 10:18 | News from kohagit: Bug 23475: Unset the storage if the values do not exist <https://git.koha-community.org[…]11af8bdaa6d358036> | |
| 10:18 | News from kohagit: Bug 23475: Use localStorage to preserve simple search values <https://git.koha-community.org[…]48424cec0a8663b9a> | |
| 10:22 | koha-jenkins | Project Koha_Master_D10 build #428: FAILURE in 2 min 20 sec: https://jenkins.koha-community[…]a_Master_D10/428/ |
| 10:23 | Joubu | mtj: there is something wrong in this failure, permission issue ^ |
| 10:24 | Oak joined #koha | |
| 10:26 | mtj | hi Joubu, yes.. it should be fixed now |
| 10:28 | huginn | News from kohagit: Correct Ubuntu versions in release notes - md <https://git.koha-community.org[…]02e187c7914534fbe> |
| 10:28 | Oak joined #koha | |
| 10:32 | koha-jenkins | Project Koha_Master_D11 build #165: FAILURE in 4 min 53 sec: https://jenkins.koha-community[…]a_Master_D11/165/ |
| 10:42 | alex_a joined #koha | |
| 10:50 | davidnind left #koha | |
| 10:53 | * fridolin | first push to stable Bug 23475 |
| 10:53 | huginn | Bug http://bugs.koha-community.org[…]_bug.cgi?id=23475 normal, P5 - low, ---, nick, Pushed to stable , Search context is lost when simple search leads to a single record |
| 10:55 | fridolin | what an emotion, back in the game 🤩 |
| 10:57 | inlibro joined #koha | |
| 11:05 | alex_a_ joined #koha | |
| 11:06 | koha-jenkins | Project Koha_Master_D9 build #1509: SUCCESS in 47 min: https://jenkins.koha-community[…]a_Master_D9/1509/ |
| 11:09 | ashimema | fridolin++ |
| 11:11 | magnuse | fridolin++ |
| 11:13 | fridolin | thanks ;) i'll try to be onboard every day |
| 11:13 | dont hesite to ping me or mail | |
| 11:19 | koha-jenkins | Project Koha_Master_U2010 build #60: SUCCESS in 56 min: https://jenkins.koha-community[…]_Master_U2010/60/ |
| 11:23 | Project Koha_Master_D10-Full build #14: SUCCESS in 1 hr 3 min: https://jenkins.koha-community[…]ster_D10-Full/14/ | |
| 11:35 | Project Koha_20.11_U16 build #3: SUCCESS in 1 hr 2 min: https://jenkins.koha-community[…]Koha_20.11_U16/3/ | |
| 11:35 | joubu: Correct Ubuntu versions in release notes - md | |
| 11:39 | tcohen | morning |
| 11:42 | khall joined #koha | |
| 11:43 | ashimema | hi tochen |
| 11:45 | cait joined #koha | |
| 11:54 | koha-jenkins | Project Koha_20.11_U18 build #3: SUCCESS in 47 min: https://jenkins.koha-community[…]Koha_20.11_U18/3/ |
| 11:54 | joubu: Correct Ubuntu versions in release notes - md | |
| 11:57 | inlibro joined #koha | |
| 12:08 | khall joined #koha | |
| 12:10 | koha-jenkins | Project Koha_20.11_D10 build #20: SUCCESS in 51 min: https://jenkins.koha-community[…]oha_20.11_D10/20/ |
| 12:10 | joubu: Correct Ubuntu versions in release notes - md | |
| 12:16 | fridolin joined #koha | |
| 12:18 | koha-jenkins | Project Koha_20.11_U20 build #4: SUCCESS in 54 min: https://jenkins.koha-community[…]Koha_20.11_U20/4/ |
| 12:18 | joubu: Correct Ubuntu versions in release notes - md | |
| 12:20 | Project Koha_20.11_D11 build #9: FAILURE in 10 min: https://jenkins.koha-community[…]Koha_20.11_D11/9/ | |
| 12:21 | Project Koha_20.05_D10 build #144: UNSTABLE in 3 hr 21 min: https://jenkins.koha-community[…]ha_20.05_D10/144/ | |
| 12:23 | Project Koha_20.11_U18 build #4: FAILURE in 5 min 7 sec: https://jenkins.koha-community[…]Koha_20.11_U18/4/ | |
| 12:25 | Project Koha_Master_D11 build #166: STILL FAILING in 5 min 19 sec: https://jenkins.koha-community[…]a_Master_D11/166/ | |
| 12:26 | Project Koha_Master_D9 build #1510: FAILURE in 5 min 5 sec: https://jenkins.koha-community[…]a_Master_D9/1510/ | |
| 12:33 | Project Koha_20.11_U2010 build #4: SUCCESS in 57 min: https://jenkins.koha-community[…]ha_20.11_U2010/4/ | |
| 12:42 | Project Koha_20.11_D9 build #6: SUCCESS in 48 min: https://jenkins.koha-community[…]/Koha_20.11_D9/6/ | |
| 12:57 | inlibro joined #koha | |
| 13:04 | Dyrcona joined #koha | |
| 13:16 | koha-jenkins | Project Koha_Master_D10-Full build #15: SUCCESS in 52 min: https://jenkins.koha-community[…]ster_D10-Full/15/ |
| 13:25 | paul_p_ joined #koha | |
| 13:26 | koha-jenkins | Yippee, build fixed! |
| 13:26 | wahanui | Congratulations! |
| 13:26 | koha-jenkins | Project Koha_20.11_D11 build #10: FIXED in 51 min: https://jenkins.koha-community[…]oha_20.11_D11/10/ |
| 13:26 | joubu: Correct Ubuntu versions in release notes - md | |
| 13:27 | Joubu | tcohen: this is new ^, jenkins is displaying the commits for each run. Do you know where it's coming? |
| 13:27 | it's only doing it for the new 20.11 apparently | |
| 13:27 | tcohen | I think it is an option on the projects |
| 13:29 | koha-jenkins | Yippee, build fixed! |
| 13:29 | wahanui | Congratulations! |
| 13:29 | koha-jenkins | Project Koha_Master_D9 build #1511: FIXED in 55 min: https://jenkins.koha-community[…]a_Master_D9/1511/ |
| 13:33 | Project Koha_20.11_U2010 build #5: SUCCESS in 59 min: https://jenkins.koha-community[…]ha_20.11_U2010/5/ | |
| 13:45 | Yippee, build fixed! | |
| 13:45 | wahanui | Congratulations! |
| 13:45 | koha-jenkins | Project Koha_Master_D10 build #429: FIXED in 42 min: https://jenkins.koha-community[…]a_Master_D10/429/ |
| 13:57 | inlibro joined #koha | |
| 14:16 | koha-jenkins | Yippee, build fixed! |
| 14:16 | wahanui | Congratulations! |
| 14:16 | koha-jenkins | Project Koha_Master_D11 build #167: FIXED in 50 min: https://jenkins.koha-community[…]a_Master_D11/167/ |
| 14:57 | inlibro joined #koha | |
| 15:00 | caroline | cait: the link for 20.11 already works https://koha-community.org/manual/20.11/en/html/ |
| 15:00 | cait1 ^ | |
| 15:05 | cait1 | yep i put those on the wiki |
| 15:06 | i need the development ones for 21.05 :) | |
| 15:06 | caroline | ah ok! |
| 15:06 | cait1 | i have commented out the "devel" manual section for now until we get the links working |
| 15:06 | caroline | I was wondering if it was necessary to do it right away... |
| 15:07 | I'd rather keep 20.11 as "master" for the time being until we start really wonrking on 21.05 | |
| 15:09 | cait1 | hm wonder if we have links for master? |
| 15:09 | we could have them | |
| 15:09 | nope not working | |
| 15:09 | it has time, i just waned to inform you as we previously had that section on the docs page | |
| 15:11 | caroline | there is "latest", but right now I think it points to 20.11 |
| 15:15 | ashimema | curse my memory for how this all fits together |
| 15:38 | cait1 | we should write it down |
| 15:38 | not keep in memory :) | |
| 15:39 | ashimema | I thought we did |
| 15:39 | cait1 | wiki? |
| 15:39 | wahanui | wiki is back :) |
| 15:39 | ashimema | but I can't remember where we wrote it :P |
| 15:39 | cait1 | thx wahanui |
| 15:39 | hm didn't we discuss in an issue on gitlab? | |
| 15:39 | ashimema | that could be it |
| 15:41 | caroline | https://gitlab.com/koha-commun[…]anual/-/issues/19 |
| 15:41 | I don't know what rangi did though, he just wrote "it's done" | |
| 15:42 | Joubu | https://koha-community.org/manual/latest/en/html/ |
| 15:42 | what's the question? | |
| 15:42 | wahanui | it has been said that the question is a bit general |
| 15:43 | caroline | How do we change "latest" to 20.11? |
| 15:44 | ashimema | I think 'latest' and the development version of the manual are different |
| 15:44 | rangi updates the symlink on the server | |
| 15:44 | hense I just mentioned him.. right now it points to 20.05 | |
| 15:44 | caroline | should we have a "latest" link and a "devel" link? |
| 15:45 | that way, there is no need to change the website | |
| 15:46 | ashimema | somewhere things will need to change each cycle |
| 15:47 | the difficultly is your treating 20.11 and 'master' as the same thing | |
| 15:47 | for an overlap period | |
| 15:47 | so whilst you do that there is no 'devel' version | |
| 15:48 | deb-CSPL joined #koha | |
| 15:49 | ashimema | the idea was to have a 'staging' area |
| 15:49 | caroline | My main issue is that we won't start documenting things for 21.05 for a while since there is really no development for at least a month, so if we branch the manual right away, I have to merge into "master" and then cherry pick into 20.11 for EACH commit |
| 15:49 | ashimema | so.. you merge your patches into the master branch, which tracks the 'next release'.. |
| 15:49 | fridolin left #koha | |
| 15:50 | ashimema | then you have a quick check that it looks ok on that devel site.. |
| 15:50 | then if needed you backport it to as many branches as you need to to reflect the change | |
| 15:50 | well.. that's how the rmaints do it ;) | |
| 15:50 | it's not necessarily the model you need to take | |
| 15:51 | * ashimema | would really like to see a near complete manual on release rather than it being months behind :( |
| 15:51 | ashimema | but that's another story |
| 15:51 | caroline | right and that's the part that takes a while because it per commit (not per merge request) so if one merge request is for 20.11 and has 10 commits, I have to cherry pick each commit independantly |
| 15:51 | ashimema | you can cherry pick a set ;) |
| 15:51 | caroline | it's not a big deal, but it's just that there won't be anything for 21.05 right away so I don't see the need to branch right away |
| 15:52 | ashimema | git cherry-pick HEAD^^^..HEAD |
| 15:52 | that would cherry-pick the latest 3 commits | |
| 15:52 | caroline | from command-line maybe, but I do it in the interface |
| 15:52 | ashimema | ah |
| 15:52 | Joubu | HEAD~3.. |
| 15:52 | ashimema | ok |
| 15:52 | caroline | I'm not git-wise enough to do it from command-line |
| 15:53 | ashimema | well.. caits just hiding the dev links for now is the easiest approach if you dont want to backport for a while |
| 15:53 | the real challenge is.. it's just you | |
| 15:53 | caroline | I really read this like I'm the challenge |
| 15:53 | ashimema | you are like the RM for the manual... but you're also acting as RMaint for the stable, oldstable and oldoldstable versions too |
| 15:53 | that's too much for just you | |
| 15:53 | Joubu | caroline: the thing is, imo, 20.11 should be created. Then when a patch is pushed to master and is about a 20.05 (or even earlier) ft/enh, you should backport it |
| 15:53 | ashimema | no, no.. not at all |
| 15:54 | Joubu is right.. | |
| 15:54 | caroline | I know you didn't mean that but that's how I read it at first lol! |
| 15:54 | ashimema | but.. it's a big job and not your fault caroline |
| 15:55 | let me have a little think | |
| 15:55 | we could branch 20.11 and set it as the 'default' branch perhaps | |
| 15:55 | then you can update the 'default' branch when you're ready to start merging for 21.05 | |
| 15:55 | * ashimema | tries to see drawbacks of that |
| 15:56 | caroline | I was thinking maybe we could branch, and then before I start merging things for 21.05, I "merge" the branch? |
| 15:56 | So that it's copied? | |
| 15:56 | ashimema | how far do you currently backport.. do you try to backport beyond one release? |
| 15:56 | caroline | I only backport if the writer tells me this is for XX version |
| 15:56 | otherwise I don't because I find it too much of a hassle | |
| 15:57 | ashimema | so... that's bad :( |
| 15:57 | our manual will never catch up that way | |
| 15:57 | caroline | well, the most up-to-date version is the latest |
| 15:57 | ashimema | you'll always need to look at a later release if you hope to see half the features in your current release documented |
| 15:58 | inlibro joined #koha | |
| 15:58 | caroline | since we're so far behind, we only write fro the current version anyway |
| 15:59 | ashimema | humm |
| 15:59 | caroline | The only times we write for other versions is when someone specifically tells us to, or in between versions like right now |
| 16:00 | ashimema | but we're not 'in between versions' |
| 16:00 | current stable is not 20.11 | |
| 16:00 | s/not/now/ | |
| 16:01 | there is no 'in between' | |
| 16:01 | Joubu | caroline: maybe you should require the info to be provided when the issue (or the merge request) opened |
| 16:01 | ashimema | either a version is release or it's not |
| 16:01 | do you really only start documenting 20.11 upon it's release | |
| 16:01 | and then spend 6 months documenting it | |
| 16:01 | caroline | What I meant was you're not "developping" for 21.05 right now, you're fixing bugs |
| 16:02 | ashimema | then drop documenting that and start documenting 21.05 upon it's release |
| 16:02 | so the docs are always at least 6 months behind | |
| 16:03 | * ashimema | feels like he's starting to sound grumpy.. so goes to get a cup of tea... we're all volunteers in these roles and he doesn't want to upset anyone.. you're doing a great job caroline |
| 16:03 | caroline | we document as it's being developped (as much as we can, which, between the 4-5 of us is not a lot), but right now, the developpers are not adding to the software, just fixing bugs, so until you guys start adding new things, I think we can continue documents what we didn't have time to document for 20.11 |
| 16:03 | Joubu | caroline: would you need more help from the authors of the features/enhs? |
| 16:04 | * ashimema | has wanted to push for manual submissions as part of the QA process.. to ensure the manual patches are created before the enhancement, change is pushed into code |
| 16:04 | caroline | Joubu: that would be great! I think ashimema tried to have the devs write at least a starter thing, but it didn't work much |
| 16:05 | Joubu | what would you need? |
| 16:05 | ashimema | we didn't push it hard |
| 16:05 | caroline | And I mean, developpers are not writers, I get it |
| 16:05 | ashimema | we could add it as a requirement |
| 16:05 | Joubu | like a more detail test plan, screenshot, more info in the "release notes" field? |
| 16:05 | ashimema | well.. it doesn't entirely require a dev to write it.. it could be someone from their company write it |
| 16:05 | caroline | Test plan is a must imo |
| 16:06 | release note would be really nice to have | |
| 16:06 | ashimema | the only real way to enforce it is to prevent the code from going in without it.. |
| 16:06 | Joubu | there should always have a test plan for new ft/enh |
| 16:06 | ashimema | i.e a hard failure at QA or RM about to push stage |
| 16:07 | personally.. I'd be happy with that.. it would give me the kick I need to either write the docs myself or beg someone here to write them for me. | |
| 16:07 | Joubu | yes, ashimema, that's exactly what I am planning to do if they need it |
| 16:07 | ashimema | I wanted to do it.. but didn't do it early enough in a cycle |
| 16:07 | and din't have the confidence to push it through | |
| 16:07 | you have my backing Joubu | |
| 16:08 | Joubu | caroline: think about what would be best for the doc team, and we will see how we can enforce rule before push |
| 16:08 | ashimema | I actually think it would make the whole SO and QA process easier if there were at least skelital submissions for the manual nice and early.. you stand a much better chance of understanding what the functionality is designed to do. |
| 16:08 | Joubu | if you tell a dev "write something or your stuff is not pushed", they will write it :D |
| 16:08 | caroline | ok thanks, I'll let you know |
| 16:08 | lol! | |
| 16:09 | Joubu | If you have something before Wednesday we could announce it during the dev meeting |
| 16:09 | ashimema | Joubu++ |
| 16:09 | caroline++ | |
| 16:10 | Joubu | I mean, if you need something more than the "release notes" field |
| 16:10 | caroline | already having text in the release notes field would be a great help |
| 16:10 | That way, we already have an idea of what we're supposedc to look for | |
| 16:12 | Joubu | everything big/important pushed to 20.11 has it |
| 16:12 | (at least now, maybe not when they got pushed) | |
| 16:17 | ashimema | are gitlab runners free for open source.. |
| 16:17 | * ashimema | is contemplating whether we can start building the manual for merge requests to get a nice preview |
| 16:19 | tcohen | they are free, there are some quotas |
| 16:19 | a while ago we set some of our jenkins nodes to work as gitlab runners and it was straight-forward to do | |
| 16:35 | caroline | ashimema: I saw you (or someone else) added a "Manual merge request" field on bz, should I do something with that once it's merged? |
| 16:35 | ashimema | I just added it as an idea to see how it might look |
| 16:36 | my thinking is.. if you choose to make it a requirement for enhancements to come with a manual submission.. we should provide an easy way to get between the two | |
| 16:37 | then QA people can fail fast if there's no link present in that field | |
| 16:37 | caroline | ok! |
| 16:38 | ashimema | but yes.. lets us know if you would like to see that done.. I can remove the field as quickly as I added it.. |
| 16:38 | twas just to see how it would look ;) | |
| 16:40 | caroline | I think david was looking into making a link between bz and gitlab, don't know what that would look like |
| 16:41 | Joubu | ashimema: why not using the "URL" field? |
| 16:41 | at least it would be clickable :) | |
| 16:41 | ashimema | because it already has mixed use |
| 16:42 | cait1 | oh wow... can someone summarize? :) |
| 16:43 | Joubu | we will try to help the doc team by making the release notes required before push |
| 16:44 | (enforcing an existing rule actually) | |
| 16:44 | and caroline is going to think if she needs something else (I suggested screenshots) | |
| 16:47 | cait1 | hm not quite existing but a great first step |
| 16:47 | we can certainly fail for missing release notes (I sometimes might writ some feeling nice) | |
| 16:48 | not sure if we can move to manual submission straight away, maybe we could start with making it an option to demand for anything we deem "new feature" | |
| 16:48 | small steps? | |
| 16:48 | so qa can say: this is a new feature (no enhancement) - please write the manual or at least submit a draft | |
| 16:49 | caroline | If you could only pass those with release notes, that would be a great help |
| 16:49 | cait1 | we can do both |
| 16:49 | :) | |
| 16:50 | but we shoud definitely put it in coding guildelines | |
| 16:50 | alexis joined #koha | |
| 16:50 | cait1 | much easier to enforce this wqay |
| 16:50 | caroline | Joubu said he'd tell everyone on Webnesday |
| 16:51 | ashimema | deffo worth a guideline |
| 16:51 | bugzilla is soo anoying sometimes | |
| 16:51 | the URL field is sued for all sorts already so I didn't want to re-use it | |
| 16:52 | cait1 | yep, let's do that AND put it in writing please :) |
| 16:52 | ashimema: agree on that | |
| 16:52 | ashimema | but you can't make a custom field a URL.. it's just plain text :( |
| 16:52 | which isn't clickable | |
| 16:52 | cait1 | hm too bad |
| 16:52 | maybe better to put in comments then too? | |
| 16:52 | ashimema | I like it at the top.. things are really easy to loose in the comments |
| 16:53 | cait1 | tcohen: I want an answer to the other 3 questions too ;) |
| 16:53 | not only the first | |
| 16:53 | hm second | |
| 16:53 | ashimema: also true | |
| 16:53 | wonder if gitlab allows tricks with jquery or so? | |
| 16:53 | um bugzilla | |
| 16:53 | wahanui | i guess bugzilla is probably right |
| 16:53 | cait1 | ok, been a long day |
| 16:53 | ashimema | nope |
| 16:53 | 'fraid not | |
| 16:54 | caroline | when you push a patch to master, it automatically sets versions released it at the version number right? |
| 16:55 | trying to find a way to have a list of things I should review for the manual keyword | |
| 16:55 | ashimema | yes and no... |
| 16:55 | we use a script to do it | |
| 16:55 | so it's not entirely automatic.. though it may look that way to you guys | |
| 16:55 | caroline | ok, but it's not manual, there's no chance it would be forgotten? |
| 16:55 | ashimema | you can basically presume it's automatic |
| 16:56 | caroline | ok +1 |
| 16:56 | ashimema | in recent cycles.. very unlikely but does very occasionally happen |
| 16:58 | inlibro joined #koha | |
| 17:08 | * cait1 | works on another presentation... |
| 17:08 | koha-jenkins | Yippee, build fixed! |
| 17:08 | wahanui | Congratulations! |
| 17:08 | koha-jenkins | Project Koha_20.11_U18 build #5: FIXED in 51 min: https://jenkins.koha-community[…]Koha_20.11_U18/5/ |
| 17:08 | cait1 | heh |
| 17:08 | slides ... everywhere. | |
| 17:09 | reiveune | bye |
| 17:09 | reiveune left #koha | |
| 17:25 | khall joined #koha | |
| 17:25 | cait1 | kf |
| 17:28 | koha-jenkins | Project Koha_20.05_D10 build #145: STILL UNSTABLE in 47 min: https://jenkins.koha-community[…]ha_20.05_D10/145/ |
| 17:33 | tcohen | hola cait1 |
| 17:33 | what are you talking about? | |
| 17:34 | cait1 | you said what you want to work on, but I want you to be a goto-person for REST among other things heh :) |
| 17:34 | qa email this morning | |
| 17:37 | tcohen: ^ | |
| 17:41 | tcohen | ok |
| 17:42 | I actually didn't mention what I want to work on, just past work that would help me do what I want this cycle | |
| 17:44 | khall joined #koha | |
| 17:52 | cait joined #koha | |
| 17:55 | tuxayo | hi #koha o/ |
| 17:55 | caroline | hi tuxayo! |
| 17:58 | inlibro joined #koha | |
| 17:58 | tcohen | hi tuxayo |
| 17:58 | cait | switching to this personality |
| 18:25 | koha-jenkins | Project Koha_Master_D9 build #1512: UNSTABLE in 3 hr 38 min: https://jenkins.koha-community[…]a_Master_D9/1512/ |
| 18:32 | marie-luce joined #koha | |
| 18:39 | paul_p_ joined #koha | |
| 18:40 | cait | rangi, ping me, when you are around? |
| 18:58 | inlibro joined #koha | |
| 19:13 | josef_moravec joined #koha | |
| 19:47 | khall joined #koha | |
| 19:48 | alexbuckley joined #koha | |
| 19:55 | caroline | anyone knows what is the commande for translate update? I do ./translate update fr-CA and it tells me I have to use gulp or something? |
| 19:56 | cait | yes |
| 19:56 | it's new | |
| 19:56 | the instructions are on the bug | |
| 19:57 | and we shoudl put them on the wiki | |
| 19:57 | sec | |
| 19:57 | bug 25067 | |
| 19:57 | huginn | Bug http://bugs.koha-community.org[…]_bug.cgi?id=25067 enhancement, P5 - low, ---, julian.maurice, Pushed to master , Move PO file manipulation code into gulp tasks |
| 19:57 | cait | it will be much faster than before |
| 19:58 | inlibro joined #koha | |
| 20:02 | caroline | thx cait I will try the new instructions |
| 20:06 | cait | gmcharlt++ |
| 20:07 | caroline: let me know if you get stuck, i tested and got it working - so maybe i can help :) | |
| 20:07 | caroline | Well, there's a step missing in the test plan, you have to install gulp :) |
| 20:07 | doing that right now | |
| 20:08 | cait | ah i already had that |
| 20:08 | creating the css files | |
| 20:12 | caroline: where do i file typos in the manual? just bugzilla? | |
| 20:12 | caroline | yes bugzila |
| 20:18 | cait, I got the error "TypeError: Cannot read property 'apply' of undefined" /usr/lib/nodejs/gulp/bin/gulp.js:132 gulpInst.start.apply(gulpInst, toRun); | |
| 20:18 | cait | hm |
| 20:18 | are you in koha-shell? | |
| 20:18 | caroline | no I'm on my git |
| 20:19 | cait | ah |
| 20:19 | hm | |
| 20:19 | i only tested in a gitified | |
| 20:19 | let's go thorugh the steps | |
| 20:19 | where did this happen? | |
| 20:19 | yarn install did run ok? | |
| 20:22 | caroline | alright le tme see, I did yarn install there's nothing in red so I assume everything's OK |
| 20:22 | cait | ok |
| 20:22 | did you install the extra package? | |
| 20:23 | i think oyu might have to get it from cpan | |
| 20:23 | install Locale::XGettext::TT2 | |
| 20:23 | caroline | Yup I did sudo cpan Locale::XGettext::TT2 |
| 20:23 | Again nothing in red | |
| 20:23 | cait | hm |
| 20:23 | caroline | then I did gulp po:update and it told me I didn't have gulp |
| 20:24 | (I'm in my misc/translator directory, even though I don't think it matters) | |
| 20:24 | then I did sudo apt install gulp | |
| 20:24 | cait | i think too late for julian to be around, but if you leave a comment on the bug |
| 20:24 | he might help | |
| 20:24 | i tihnk it worked for me | |
| 20:25 | but kohadevbox, so not sure if the env matters | |
| 20:58 | inlibro joined #koha | |
| 21:07 | caroline | ok I think I got it running.... I had to update node and npm (I think) |
| 21:09 | cait | oh |
| 21:09 | but good work | |
| 21:13 | caroline | But the string I wanted to translate is not translating anyway T_T |
| 21:13 | cait | oh |
| 21:13 | not showing up in the po? | |
| 21:14 | caroline | I see it in the po |
| 21:14 | cait | ok |
| 21:14 | but it doens't install? | |
| 21:14 | caroline | I did translate install fr-CA |
| 21:14 | cait | how does it look in the po |
| 21:14 | fuzzy by chance? | |
| 21:14 | caroline | not fuzzy |
| 21:14 | It looks normal | |
| 21:15 | in the po https://snipboard.io/M1RrFL.jpg | |
| 21:15 | in the installer https://snipboard.io/8D1uFZ.jpg | |
| 21:16 | it's so weird, some strings are translated, some are not from fr-CA-installer-MARC21.po | |
| 21:18 | cait | hm ot sure about that one |
| 21:18 | maybe file a bug? | |
| 21:18 | did joined #koha | |
| 21:21 | caroline | is this sentence in German for you? |
| 21:23 | cait | Sorry, I can't check right now |
| 21:23 | caroline | np |
| 21:48 | khall joined #koha | |
| 21:51 | ivandz joined #koha | |
| 21:52 | ivandz | Hi all! |
| 21:53 | What is version ElasticSearch for Koha 20.11? Thanks! | |
| 21:54 | cait | i believe 6 from the bug reports |
| 21:54 | bug 22520 | |
| 21:54 | huginn | Bug http://bugs.koha-community.org[…]_bug.cgi?id=22520 enhancement, P5 - low, ---, koha-bugs, NEW , Be Elastic compliant 7.x and 8.x (_doc) |
| 21:54 | cait | bug 25439 |
| 21:54 | huginn | Bug http://bugs.koha-community.org[…]_bug.cgi?id=25439 enhancement, P5 - low, ---, koha-bugs, NEW , [Omnibus] Prepare Koha to ElasticSearch 7 - ES7 |
| 21:55 | cait | it appears support for 7 is not done yet |
| 21:55 | ivandz | 6 it's ok? |
| 21:55 | if I use it | |
| 21:56 | cait | i am not using it myself, so if you want ot make sure, maybe someone else will now |
| 21:58 | ivandz | kidclamp: Hello! |
| 21:58 | cait, thanks! | |
| 21:59 | inlibro joined #koha | |
| 21:59 | ivandz | @kidclamp Are you here? |
| 21:59 | huginn | ivandz: I'll give you the answer as soon as RDA is ready |
| 21:59 | wahanui | i already had it that way, huginn. |
| 22:00 | ivandz | huginn, thanks! |
| 22:00 | huginn | ivandz: I'll give you the answer just as soon as RDA is ready |
| 22:00 | wahanui | i already had it that way, huginn. |
| 22:13 | khall joined #koha | |
| 22:31 | khall joined #koha | |
| 22:47 | khall joined #koha | |
| 22:54 | cait1 left #koha | |
| 22:59 | inlibro joined #koha | |
| 22:59 | khall joined #koha | |
| 23:03 | khall joined #koha | |
| 23:08 | ivandz joined #koha | |
| 23:53 | khall joined #koha | |
| 23:59 | inlibro joined #koha |
← Previous day | Today | Next day → | Search | Index