IRC logs for #farmOS, 2023-03-07 (GMT)

2023-03-06
2023-03-08
TimeNickMessage
[08:54:44]<symbioquine[m]><mstenta[m]> "I put together a first pass at..." <- This is going to be awesome documentation to have! Left a few minor review comments.
[08:54:45]<lordeddi[m]>Hi there, there is an admin here in this room. Though im not sure what the admins time zone is...
[08:54:56]* DavidWilson[m] has joined #farmos
[08:54:57]<DavidWilson[m]>Hello, how can I contact any admin of farmier? I sent an email, but i have no response
[15:06:05]<mstenta[m]>I'll send you a direct message... standby...
[15:06:06]<DavidWilson[m]>Oh I see :( please read my email
[15:06:06]<symbioquine[m]><mstenta[m]> "I put together a first pass at..." <- Left a couple more comments/questions, but otherwise 🚢
[15:06:06]<DavidWilson[m]>s/email/mail/
[15:06:06]<mstenta[m]>I don't see an email from you, however. 🤔
[15:06:06]<mstenta[m]>Hi David Wilson I'm the one to talk to :-)
[16:07:16]<mstenta[m]>paul121 symbioquine: just had another thought with regard to our open question: "does farmOS need to increase its major version to 3.x for Drupal 10"...
[16:08:28]<mstenta[m]>I think we do, if only because it will then require any custom/contrib modules to update their composer.json files to farmos/farmos ^3.0 to indicate their compatibility with D10
[16:09:09]<mstenta[m]>Otherwise there's a risk that they aren't actually compatible with ^2.0 anymore
[16:11:03]<mstenta[m]>So just like Drupal needs to increase it's major version alongside Symfony major versions, I think we do as well
[16:15:40]<FarmerEd[m]>That makes sense.
[16:18:17]<FarmerEd[m]>But it could put the fear into some folks that it would be like moving from 1.x to 2.x
[16:20:02]<mstenta[m]>Then they will be pleasantly surprised when it isn't! 😄
[16:29:42]<paul121[m]>Makes sense. Probably means modules need to make a major release as well
[16:30:32]<mstenta[m]>Perhaps - but maybe only if they make major changes?
[16:30:34]<mstenta[m]>Or... oh because they might try to use them on v2?
[16:31:18]<paul121[m]>I think?
[16:31:52]<paul121[m]>I mean, if you bump the modules farmOS/farmOS dependency up a major version. It seems like the same argument as Drupal following Symfony major versions
[16:33:31]<FarmerEd[m]>Will it not be the case that many modules will be simultaneously compatible with Drupal 9/10
[16:33:48]<mstenta[m]>Yes that's true too
[16:34:03]<mstenta[m]>So yea it'll probably be a case-by-case if they need a major version increment
[16:34:51]<mstenta[m]>and in their `composer.json` they can have `"farmos/farmos": "^2.0 || ^3.0",` to indicate that they work for both
[16:35:16]<mstenta[m]>but it will be necessary for them to add the ^3.0 manually as a way to indicate that they have indeed confirmed that they are compatible
[16:39:20]<mstenta[m]>commented on our tracking issue to reference this conversation: https://www.drupal.org/project/farm/issues/3330490#comment-14956960
[16:47:41]<symbioquine[m]>I don't think I'll support 2.* for any of the modules I maintain once a 3.* is out and stable. I'd rather have less surface area to test/support - especially if it's a trivial migration effort between the two.
[16:54:52]<FarmerEd[m]>At least you got a stable 2.0 out before 3.0 😄
[16:55:32]<mstenta[m]>Yea, well it's also hard to say when we'll be able to jump to D10
[16:55:33]<mstenta[m]>Depends on dependencies
[16:55:43]<mstenta[m]>A story as old as time