00:00:40 <Denyerec> the contact form errors are so far my favourite part :)
01:01:17 <Outdoorsman> @danilobuerger Just so you know I've been working to upgrade to PHP 5.4 ever since your comment earlier today. I still have probably 2 hours left.
01:04:10 <Outdoorsman> Whew. Part of the reason I hadn't upgrade is because until Jan 21 of this year, Magento didn't support PHP 5.4. They released a patch that can be applied at least back to Magento version 22.214.171.124. http://www.magentocommerce.com/blog/magento-now-supports-php-54/
01:04:35 <Outdoorsman> Just thought I'd share. Thanks again for the tip though :)
02:09:54 <danilobuerger> Denyerec still need help?
02:10:01 <danilobuerger> Outdoorsman finished your upgrade?
16:55:20 <NamelessCoder> essentially jkphl - how can we help you *without* taking on more work? ;)
16:55:22 <jkphl> just wanted to say: it's definitely not my intention to just get you more workload. so i totally understand your concerns ... but:
16:57:58 <jkphl> there's really nothing special to understand (or not understand) about bower. it's just that this "bower.json" file has to sit in the repo, that's all. most of my projects do support bower, and there hasn't been even one case when someone needed support because of *this*.
16:58:16 <jkphl> still, the version number inside the file should be up to date, that's correct.
16:58:31 <jkphl> and someone has to do this (just like with the composer files as well)
16:58:50 * Denyerec is using bower in his fedext template
17:01:31 <NamelessCoder> jkphl we change this version number already 2x2 times for every extension on every TER release - we update composer.json, then let EM upload and update ext_emconf.php, then commit this as a [TER] Release and do it all again to set the version to x.y+1.z BETA and push
17:01:37 <jkphl> as i said, unfortunately i'm neither an expert on all of this - bower, git / github, deployment and so on. i'dalso love to know a reasonably easy way to keep all the version numbers in sync, e.g. of extensions lying on github, in the TER and as github releases
17:02:34 <cedricziel> we should investigate if a build chain (i am thinking about atm) would support this
17:02:37 <NamelessCoder> we *really* need to have this automated before we can accept such maintenance
17:22:04 <jkphl> ok guys, thx for the discussion! need to work on something different now, spent way more time on this today as i could afford ... :/ there are only 1.5 weeks left until my only holidays this year, and i'm working on 14(!) projects in parallel atm ... oh man, i'm really exhausted ...