14:00:03 #startmeeting Fedora Infrastructure Sustaining Standup Meeting 14:00:03 Meeting started Thu Jun 25 14:00:03 2020 UTC. 14:00:03 This meeting is logged and archived in a public location. 14:00:03 The chair is mkonecny. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:03 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:03 The meeting name has been set to 'fedora_infrastructure_sustaining_standup_meeting' 14:00:03 #chair cverna mkonecny siddharthvipul jednorozec mboddu lrossett asaleh mobrien nils pingou 14:00:03 Current chairs: asaleh cverna jednorozec lrossett mboddu mkonecny mobrien nils pingou siddharthvipul 14:00:03 #info meeting is 30 minutes MAX. At the end of 30, its stops 14:00:03 #info agenda is at https://board.net/p/fedora-infra-daily 14:00:14 .hello zlopez 14:00:14 mkonecny: zlopez 'Michal Konečný' 14:00:15 .hello lrossett 14:00:17 lrossett: lrossett 'Leonardo Rossetti' 14:00:24 .hello nphilipp 14:00:24 nils: nphilipp 'Nils Philippsen' 14:00:59 .hello siddharthvipul1 14:01:00 siddharthvipul_: siddharthvipul1 'Vipul Siddharth' 14:02:25 Do we want to start or wait a little longer for others? 14:03:11 lets start 14:03:33 a 5min wait is more than enough 14:03:44 #topic Members reports 14:03:44 #info we will go one by one saying our full report 14:03:44 #info Done - What you did from last standup? 14:03:44 #info In progress - What you are working on? 14:03:44 #info Need review - Do you have anything that needs to be reviewed? 14:03:45 #info Blockers - Are you blocked by anything? 14:03:46 #info Next - Nominate next one who will report - look at the Current chairs printed by zodbot 14:03:59 lrossett: You are first 14:04:26 updated my shared mbs just a few minutes ago which is being reviewed already, no blockers 14:06:01 lrossett: Anything else or should I continue? 14:06:07 nope, next is mkonecny 14:06:08 sorry 14:06:33 Nothing happened, it's just hard to know if you are done on IRC 14:06:36 Done: Update Anitya buildconfig in production 14:06:36 In progress: Review of MBBox PR 14:06:36 In progress: Remove current alembic migrations in Anitya 14:06:36 Need review: Add towncrier to the-new-hotness https://github.com/fedora-infra/the-new-hotness/pull/300 14:06:37 Blockers: Can't test packit integration in the-new-hotness, no staging environment for now 14:06:55 Next: nils 14:07:37 sec 14:08:11 Done: enhanced Pagure git hook link checking script 14:08:43 Done: updated documentation for Infra Ansible in Pagure with recent changes 14:09:25 In (Slow) Progress: Mailman3 (#8445) 14:09:49 Next: siddharthvipul_ 14:10:00 \o/ 14:10:21 yess, so I have been working with tenants to migrate them over to new cluster. So far it's going great and we have created a place for 6 projects so far (already). 14:10:31 no blocker so far :) 14:10:35 14:11:00 since my name was last, mkonecny open floor already? 14:11:02 siddharthvipul_: Does tox project tested in CI need to do anything? 14:11:10 #topic Open floor 14:11:10 #info You can ask anything you want, or bring a topic to discuss 14:11:24 fedora-apps namespace? 14:11:26 I will take that 14:11:33 I will migrate the whole thing 1 by 1 14:11:43 siddharthvipul_++ 14:11:52 ^^ 14:12:25 Other thing I wanted to talk about is the deletion of alembic migration 14:12:40 Does anybody know how to do this correctly? 14:13:16 Right now I removed every migration that exists except the last one, which downgrades to None revision 14:13:46 This looks good and it's working 14:14:09 mkonecny, you mean you don't need all that history any longer? 14:14:24 I know that Bodhi is removing the old migration when doing a new major version 14:14:57 nils: The migrations are not needed if the database is already up to date 14:15:01 Has the number of alembic migrations become unmanageable? 14:15:33 I had around 20 migrations in Anitya 14:16:12 Which is I think too much 14:16:47 That's not too much. You might want to keep them around if you need to test older revisions. As far as I know there is no real downside to keeping the migrations other than the files consuming space. 14:17:20 nils: So you think that this is not worth the work around it? 14:17:22 Playing devil's advocate, why is this too much? 14:17:33 Just my feeling 14:18:06 I seem to recall that Bodhi had hundreds of migrations so cleaning those of previous major versions made sense. 14:18:27 So no real reason, except I want to prepare Anitya for 1.0 14:19:20 And also check if there is no issue when removing the migrations 14:19:25 If somebody else has an Anitya 0.9 (no idea if this version exists, but this holds even for a development DB), they might want to be able to upgrade and migrate to 1.0 14:19:27 No missing things in db 14:20:23 You can migrate without issue, because the db is already up to date 14:20:39 I'm just testing this on production backup 14:20:55 So people coming from an older state would first have to update to some pre-release that has the migrations, migrate, then upgrade to 1.0? 14:22:12 Skipping a few versions is never a good idea if db is part of the app 14:22:55 But yes, I will probably close this issue, because it has no real value than cleaning of the old code 14:23:21 And starting with the clean state with new major version 14:24:18 Not really needed 14:24:30 Thanks nils for your opinion 14:24:42 you're welcome 14:25:20 I will just fix some small issues around setting up anitya with empty db 14:25:31 Let's end the meeting than 14:25:44 #topic Ending meeting 14:25:45 #info Thank you all for coming. See you next on next meeting. 14:25:45 #endmeeting