An "unbitrot test suite" #DBIC 0.082841 just sailed onto CPAN
Virtually no changes within lib/, thus there is no reason to test/upgrade
0.082850 should take place in the next couple months based on https://t.co/eaunKBNU5m
Happy search()ing
Retirement: I'm doing it wrong 🙄😒
🚬 https://t.co/CyDkNkRbgp with minimal fixes to unblock @charsbar's work on DBD::SQLite, and to work around recent... "developments"
Another maint ~end-feb to address #CPANTesters lockups, and other pressing fixes
Then https://t.co/5gG3UmqS8z https://t.co/IMVmEYO2cj
Many thanks to @DRichardHipp and @charsbar for lightning-fast diagnosis and fix of #DBIC's last outstanding convoluted failcase
Report: https://t.co/vUZgcpn09i
Analyzis: https://t.co/2S14aJqiTu
Fix: https://t.co/p2JzGJ0JHi
👍👍👍
On my end $work is unexpectedly busy plus #34C3 approaches fast.
As much as I'd want to restart #DBIC dev during 2017, it can't happen before mid-Jan
The hoops through which I need to jump to work around PAUSE's "verdict" are rather involved, and have to be done just right
🕰️ https://t.co/YNKU7ytbmX
#Perl5#PSA: a recent release of Hash::Merge contains a number of subtle breaking changes touted as "bugfixes" (e.g. https://t.co/wom5O8JZUp )
Be careful when upgrading, test extensively, and have a clear path to rolling back
#DBIC still relies on H::M, hoping to rectify by Jan
A short update on the state of my work on #DBIC https://t.co/zoimQKVqak
Hoping to have more to share soon
Until then - patience 🕰️ https://t.co/QlLxKZSzj4
Re #DBIC state https://t.co/PlL4dCJqMM
Project IS actively looked after,❓s promptly answered privately
#CPAN updates once concerns addressed https://t.co/1UPiUY8w1D