Chris,<div><br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><p>
&gt; Also, I have a correction to Chris&#39;s response: we will not need two separate sets of DB changes because I will be copying every non-linear update into <a href="http://updatedatabase.pl" target="_blank">updatedatabase.pl</a>. That was the reason for the CheckVersion() routine.<br>


&gt;</p>
</div><p>Hi </p>
<p>While that is a good idea, and will mean the packages aren&#39;t totally busted on master. A commit that has both the old safe updatedatabase and the new system is no use for cherry-picking to stable.  It won&#39;t apply. So we will need a commit with just the bug fix, then another 2 commits, one doing old db update, one doing new, and I will just cherry pick the old one. </p>


<p>IE if something is needed for 3.10.x or 3.8.x it can&#39;t combine the db update part of the patch with the rest, for it to be able to apply.</p></blockquote><div><br></div><div>Sure it can. The DB update for 3.12+ will be a new file (which will be ignored by every version up until 3.12), every time. Any patches that make changes to the update system itself will have to be on different bugs, of course, but I was going to require that anyway.</div>
<div><br></div><div>Regards,</div><div>Jared</div><div> </div></div>-- <br>Jared Camins-Esakov<div>Bibliographer, C &amp; P Bibliography Services, LLC</div><div>(phone) +1 (917) 727-3445</div><div>(e-mail) <a href="mailto:jcamins@cpbibliography.com" target="_blank">jcamins@cpbibliography.com</a></div>
<div>(web) <a href="http://www.cpbibliography.com/" target="_blank">http://www.cpbibliography.com/</a></div>
</div></div>