| 27 May 2023 |
 lolgab#6138 | * We should also try to backport as more new APIs as possible and deprecate the removed APIs in the 0.10.x branch, so plugins developers can update to the last 0.10.x version and hopefully have the same sources compile with both version and have an easy migration path, once fixed all the deprecations. Updating my plugins wasn't easy at all and I don't want to put this burden to people maintaining internal closed source mill plugins | 12:17:24 |
 Tobias Roeser | Yeah, most of the recent larger refactorings don't provide any kind of source backward compatibility. Please add your issues to https://github.com/com-lihaoyi/mill/discussions/2462, so we can address them. Either in form of some intermediate @deprecated API and/or as documentation. | 12:19:19 |
| Tobias Roeser | I think backporting the new API is a lot of work and sometimes impossible. But we can add some @deprecations and try to add some @deprecated source-compatibilities API to the current version | 12:28:24 |
| Tobias Roeser | * I think backporting the new API is a lot of work and sometimes impossible. But we can add some @deprecations to the older branch and try to add some @deprecated source-compatibilities API to the current branch. | 12:28:52 |
 Haoyi#4275 | let's plan to do 0.11.0-final following Tuesday, 6 June. It's a short timeline, but I'd like to advertise it at Scaladays, which is an opportunity that doesn't come about very often
I'll go fix the versioned documentation and get started with a migration guide based on my own experience updating com-lihaoyi, but you guys will need to do the plugin-compatibility/migration stuff since you're the ones with experience maintaining plugins. | 12:33:56 |
| Tobias Roeser | That's a tough plan, at least for me personally. But I'm ok with it. | 12:37:02 |
| Haoyi#4275 | I think the most important thing to get in is any code changes, deprecated forwarders etc. to make your own plugin cross-builds easier.
It's probably OK if the migration guide comes out a day or two later. Most people with big existing builds probably aren't going to be updating on the first day of the new release. I expect it'll be a WIP over some time anyway, as people report issues or ask questions that'll give us more stuff to add that we overlook initially | 12:45:09 |
| lolgab#6138 | Also we know how to release new apis in a backward compatible way, so we can have a 0.11.1 to introduce new APIs etc. | 13:37:34 |
| lolgab#6138 | Download message.txt | 13:50:17 |
| lolgab#6138 | Edit: We can list the new APIs using MiMa. This is the result of running MiMa on the 0.10.x branch against 0.11.0-M10 in forward mode (mill-scalalib only). | 13:50:17 |
| 28 May 2023 |
|  Gromph joined the room. | 04:03:32 |
| 29 May 2023 |
|  dubujianghu joined the room. | 08:27:04 |
|  qp joined the room. | 10:30:37 |
|  natsukagami joined the room. | 12:43:19 |
|  Maximiano joined the room. | 17:48:02 |
|  araknafobia joined the room. | 18:40:30 |
|  Mr. Alpaca changed their display name from Mr. Alpaca to Mr. Alpaca#8827. | 18:54:05 |
| Mr. Alpaca changed their display name from Mr. Alpaca#8827 to Mr. Alpaca. | 18:54:09 |
| 30 May 2023 |
|  sahithi_ joined the room. | 08:15:08 |
|  danicheg joined the room. | 08:45:20 |
| natsukagami changed their display name from natsukagami to natsukagami#8648. | 10:55:25 |
| natsukagami changed their display name from natsukagami#8648 to natsukagami. | 10:55:29 |
|  Kordyjan joined the room. | 14:32:41 |
|  Axyria changed their display name from Axyria to Axyria#8788. | 16:13:45 |
| Axyria changed their display name from Axyria#8788 to Axyria. | 16:13:49 |
|  trent1967b joined the room. | 21:02:24 |
|  ysthakur joined the room. | 21:56:00 |
| 31 May 2023 |
|  dacampos joined the room. | 02:16:03 |
|  wompowe joined the room. | 20:49:53 |
| 1 Jun 2023 |
|  tuzonghua joined the room. | 15:47:21 |
