Monday 26 March 2012 3:49:05 pm - 7 replies
Introduction
Today were released 5 related security advisories. Please read carefully and take actions with no delay.
Tuesday 27 March 2012 11:40:48 pm
Thanks for the positive thoughts guys. You are 100% right. It feels good to have an engaged community, pushing relentlessly for the right things. The initial impulse came from here : http://share.ez.no/forums/developer/security-advisories/(offset)/last and I am working to quickly solve the entire initial request.
Keep-up !
Cheers,
Modified on Tuesday 27 March 2012 11:41:51 pm by Nicolas Pastorino
Wednesday 28 March 2012 9:55:32 am
Thank you for the fixes!
When will there be a version 2012.3 on https://github.com/ezsystems/ezpublish/downloads ?
Wednesday 28 March 2012 10:22:47 am
Quote from Patrizio Bekerle :Thank you for the fixes!
When will there be a version 2012.3 on https://github.com/ezsystems/ezpublish/downloads ?
Hi Patrizio,
eZ Publish Community Project 2012.3 will soon be built, including the fix, and made available under http://share.ez.no/downloads, as well as under the usual DL places like the on you mentioned.
Cheers,
Wednesday 28 March 2012 10:53:12 am
Quote from Nicolas Pastorino :Quote from Patrizio Bekerle :Thank you for the fixes!
When will there be a version 2012.3 on https://github.com/ezsystems/ezpublish/downloads ?
Hi Patrizio,
eZ Publish Community Project 2012.3 will soon be built, including the fix, and made available under http://share.ez.no/downloads, as well as under the usual DL places like the on you mentioned.
Cheers,
Thanks a lot!
Wednesday 28 March 2012 5:51:20 pm
One point I can't understand so far that as you warn your customers about the issue and provided patch 2 weeks before this announcement. Why eZ 4.7 and 2012.3 are not published at the same time you communicate on the issue ?
If I were you, I would have done it this way. I agree patches are available but it may have been easier for people to get a full version (whatever it is a community/entreprise one) than to get patches.
If it's just a delay, then you could have waited one week more...
You must be logged in to post messages in this topic!