Release v2.0

[MatthewDaggitt]

Okay, so I realise I've been somewhat absent recently. My current job ends on September 12th and my next one doesn't start until late November, so I plan to get v2.0 out the door during that period of time. I promise I will wade through the back log of PRs that have built up 👍

[jamesmckinna]

Congratulations on the new job! 🎉

[jamesmckinna]

As to managing the backlog, as both a contributor to making the pile grow, as well as more recently, helping to whittle it down (at least a little bit), I was interested to read that our colleagues on the main Agda issue tracker are correspondingly concerned about their own policies to manage their PR backlog.

It might be worth a separate issue, but rather than generate more clutter for the time being, I'm linking it here while our efforts are directed towards the v2.0 backlog... once that's out, suggest we (re)start the conversation about how to manage the way forward.

[MatthewDaggitt]

Okay, with the merge of #1895 I'm going to get serious about making a release.

As of now, all new PRs will get a v2.1 milestone unless they explicitly address an issue that needs to be fixed before v2.0.

Existing open PRs will be triaged depending on how easy they are to merge.

When would interested people be available for a meeting next week to discuss outstanding PRs? If you are, please state your availability in GMT below:

Matthew

• Monday 2nd - 7am - 4pm
• Tuesday 3rd - 7am - 11am, 2pm-4pm
• Wednesday 4th - 7am - 4pm
• Thursday 5th - 7am - 4pm
• Friday 6th - 7am - 11am

[Taneb]

My availabilities next week:

• Monday 6-7am, 7:30-9am, 10:30am-late
• Tuesday 6-7am, 8am-12pm, 2pm-late
• Wednesday 6-7am, 7:30am-late
• Thursday 6-7am, 7:30am-12pm, 2pm-late
• Friday 6-7am, 7:30am-12pm, 1:30pm-late

Note that we're in summer time! The UK is one hour ahead of GMT, much of Europe is two hours ahead.

[jamesmckinna]

This is great news!

As for a meeting next week, I'm a bit all over the place at the moment, as evidenced by the manic PR/issue/commentary explosion. Will try to identify times to meet soon!

I've been working on 'one last' (sic) branch for the AlmostCancellative issues (the corresponding ones for Monotonic can wait, but it might be good to try to knock those off as well), so I hope we can merge that/them. But: up for discussion ;-)

Ahead of such discussion, I've been making 'bids' against my own open issues and PRs (and some others) by tagging them with v2.0 (wish-to-fix-now), v2.1 (can wait) and v3.0 (I'd like it one day). Suggest others do same?

[JacquesCarette]

Next week is tricky for me: the good part, I'll be in Europe, so time zones less of an issue; less good from an availability perspective: I'll be in Dagstuhl. So while it is quite likely that I could get out for an hour, knowing when that'll be is essentially impossible to know now.

So: schedule it, and I'll see.

[jamesmckinna]

I'll be largely free-but-frazzled next week, so let me know when works best for you and @Taneb , and let's see how we do...

[MatthewDaggitt]

Okay, let's go for Wednesday 7:30am GMT then. Whoever is around is welcome to join.

[MatthewDaggitt]

Meeting link here: https://meet.google.com/trh-fpbj-kfi

[jamesmckinna]

Not really a separate issue, but to note here: before release, we should nitpick the CHANGELOG to satisfy ourselves it makes global as well as local sense (orphaned/duplicated comments; list of deprecations/additions getting out of alphabetical/file contents order, spellcheck, fix-whitespace, ...)

[Taneb]

https://time.is/730_4_Oct_2023_in_UTC

[MatthewDaggitt]

Not really a separate issue, but to note here: before release, we should nitpick the CHANGELOG to satisfy ourselves it makes global as well as local sense (orphaned/duplicated comments; list of deprecations/additions getting out of alphabetical/file contents order, spellcheck, fix-whitespace, ...)

Yup, that's always necessary before a release! I usually do it as the last possible thing though, otherwise you get horrendous merge conflicts with open PRs.