*Almost a week to go until Umbraco Together (Hacka...
# social
w
Almost a week to go until Umbraco Together (Hackathon) Curious is there anything you want to hack on specifically if your attending or want help with.
Let me or @Sebastiaan know if there is anything specific šŸ˜„
r
I don't know .. depending on audience a good old fashioned install session for some how to fork and pull request and tips on writing the pull request to make things more successful may be a package specific hackathon ie people with packages that want need help
swanky techniques for the new blocklistgridlistblockrowlist grid thing
obviously others will have much better ideas and choose those before any of mine
w
Yep all good suggestions. As always I am more than happy to help people get upto speed or do anything. Looking forward to this šŸ˜„
m
Going to finally focus on moving my blog to cloud!
w
OK sounds fun. When you say cloud. You mean Umbraco Cloud of course šŸ˜›
m
Yes!
r
may also work on something umbraco cloud related
w
Well we would love you to do stuff with Umbraco Cloud ā˜ļø And happy to make sure you have a nice experience with it so lets us know Matt & Ravi šŸ™‚
l
I've had zero chance to look at v11-RC yet, so no idea if Contentment works on it (or not). Hackathon would be a good opportunity for me to make sure that it works, etc. Other than that, if there's a record-breaking attempt for the most Umbraco core bug fixes in a day, I'll help with that too. šŸ˜…
s
v11 should hopefully be a non-event Now for most core bug fixes... That's a great challenge! 😁😁
l
bah! turns out there's a breaking change introduced in v11 (as opposed to something deprecated in v9 and removed in v11). https://github.com/umbraco/Umbraco-CMS/pull/13287#issuecomment-1328080751 so needed to release a new Contentment version. šŸ˜… (ah, feels like the good old days of Umbraco, apologies for my sarcasm 🤔 )
s
We're still looking into how to not make it breaking šŸ¤ž Guess it's too late since you already made a new release and wouldn't want to revert to a method that will be obsolete in the future, but hopefully should help other people.
Ah you've also been talking on GitHub with them šŸ‘
l
Thanks Seb! šŸ¤— Bjarke is calming my woes šŸ˜… I had to add support for v11 to Contentment anyway because I had a dependency on the SQL Server libraries (there's a SQL data-source for the Data List editor), so I wouldn't want that hard dependency on SQL Server directly (that's a separate concern). But original my concern of breaking-changes, was more that I was expecting a slower/stable pace (and not me panicking the weekend before - it wasn't a big panic).
s
Totally agreed! As far as I understood this was an accidental break and glad you found it just before (but no drama either if found in the 11.0.0 release, can patch this one to be non-breaking). We're happy for the feedback and help here! šŸ™
l
All cool 🤘
Although this does lead me to the cheeky question (which I kinda already know the answer) ... didn't HQ say they'd test against popular packages prior to a release? šŸ™‰ šŸ™Š šŸ™ˆ (I mean, Contentment might not be considered a popular package, 🤣 )
s
Yeah well, that was an nh idea thrown onto Twitter as a "policy" šŸ™ˆ Most of all, there should've been unit tests to catch this IMO.
3 Views