<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Yes, I understand that.<div><br></div><div><span style="font-size: 12pt;">Some compatibility should be provided up till next 2 versions. </span>I feel, it should be core's responsibility to provide backwards compatibility for themes using masonry v2. I don't know how to explain this, but isn't it quite obvious?<br><br><div><hr id="stopSpelling">From: jpollock412@gmail.com<br>Date: Sat, 23 Nov 2013 16:10:58 -0500<br>To: theme-reviewers@lists.wordpress.org<br>Subject: Re: [theme-reviewers] Upgrading Masonry In Core<br><br><div dir="ltr">I made a new diff based on your feedback. Thanks. BTW I wouldn't go as so fat as to say 'this upgrade is being made.' Until we get this tested throughly, ie someone runs the unit tests on it, and we attract some interest from the project leads, it's not going to get made.<div>
I guess the breaking themes issue is more of a issue of policy and/ or philosophy. Yes the upgrade will break stuff. Is it the responsibility of core to write in the backwards compatibility or is it responsibility of theme/plugin developer to fix it.</div>
</div><div class="ecxgmail_extra"><br><br><div class="ecxgmail_quote">On Sat, Nov 23, 2013 at 4:01 PM, Rohit Tripathi <span dir="ltr"><<a href="mailto:rohitink@live.com" target="_blank">rohitink@live.com</a>></span> wrote:<br>
<blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex;">
<div><div dir="ltr">Hi. I have Replied to the ticket with a few more changes that needed to be made in the diff you submitted. <span style="font-size:12pt;">Its great to see, that this upgrade is being made.</span><div><br>
</div><div>Answer to your other Question. Yes, themes are likely to suffer with this upgrade, as 5 of the very commonly used parameters were renamed in masonry v3. Hence, some sort of backword compatibilty is needed.<br>
<div>
<br><div><hr>From: <a href="mailto:jpollock412@gmail.com" target="_blank">jpollock412@gmail.com</a><br>Date: Sat, 23 Nov 2013 15:36:46 -0500<br>To: <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
Subject: [theme-reviewers] Upgrading Masonry In Core<div><div class="h5"><br><br><div dir="ltr">We discussed the need to upgrade Masonry in core to version 3 awhile back. I have submitted a new patch that not only updates Masonry to version 3 but also addresses the fact that doing so initially broke the footer widgets in 2013 and 2014 due to the different way that v2 and v3 handle column width.<div>
<br></div><div><a href="http://core.trac.wordpress.org/ticket/25351" target="_blank">http://core.trac.wordpress.org/ticket/25351</a><br></div><div><br></div><div>This raises a relevant question:</div><div>Would anyone's theme experience a similar issue? Probably. Is that a valid objection to upgrading in core?</div>
<div><br></div><div>BTW If anyone has a second to test and/ or improve on my patch it would be appreciated. I'd like to get this fairly simple upgrade done soon.</div></div>
<br></div></div>_______________________________________________
theme-reviewers mailing list
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a></div></div></div> </div></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________
theme-reviewers mailing list
theme-reviewers@lists.wordpress.org
http://lists.wordpress.org/mailman/listinfo/theme-reviewers</div></div> </div></body>
</html>