HI,<br><br><div class="gmail_quote">On Thu, Jan 5, 2012 at 6:15 PM, Johan Tibell <span dir="ltr">&lt;<a href="mailto:johan.tibell@gmail.com">johan.tibell@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">&gt;&gt; c) You are not allowed to add new instances. I don&#39;t get this - how is</div><div class="im">
&gt;&gt; this any worse than b)?<br>
<br>
</div>You cannot prevent the import of new instances. When you import a<br>
module you get all its instances. This means that explicit import<br>
lists can&#39;t protect you.</blockquote><div><br></div><div>What I don&#39;t get is how a new instance may break existing code. Any example? </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Bugfixes you be in bugfix releases (i.e. bumps to the 4th version component.)</blockquote><div><br></div><div>I though I would do without the patchlevel component at first.</div><div><br></div><div>If I understand correctly, you would recommend:</div>
<div><br></div><div>- Mayor Version changes: as described in the guidelines: changed interface, new instances</div><div>- Minor version change: when I just add functions</div><div>- Patchlevel change: for bugfixes, performance fixes, documentation changes</div>
<div><br></div><div>Thanks,</div><div><br></div><div>Chris</div></div>