Hi,<br><br>a new version of mgmt model is required when change is incompatible with previous model.<br>basically if you would take your current model and try to apply it to previously released version of subsystem, would it work?<br>
If no, then new version is required & transformers has to be written to make sure compatibility in domain mode is preserved.<br>As for transformers go, I just started working on guide to help people out, you can find it at <a href="https://docs.jboss.org/author/display/AS72/Transformers">https://docs.jboss.org/author/display/AS72/Transformers</a> (wip atm)<br>
<br>We agreed that version bump in master should be done only on major & minor flags, micro version is reserved for 7.1/EAP branches.<br>in this concrete case, change was done to 7.1 branch and same one was applied to master, hence master got just micro version bump, provided that jacorb subsystem didn't have any other changes that are in 7.1 branch.<br>
<br>To go to details, change of that validator also changed the model, where min-value was now different this would cause model that worked on new definition could fail on old one.<br><br>--<br>tomaz<br><br><br><div class="gmail_quote">
On Sat, Oct 6, 2012 at 4:15 PM, Jaikiran Pai <span dir="ltr"><<a href="mailto:jpai@redhat.com" target="_blank">jpai@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Was just looking at some of the PRs and noticed that after a recent<br>
change to Jacorb subsystem [1] we decided to bump the micro version of<br>
that subsystem's management API [2]. What are the general guidelines<br>
when it comes to bumping the management version of a subsystem? As far<br>
as xsd changes are concerned, for EJB3, I've been making sure that the<br>
version is bumped whenever there's a semantic change from a previous<br>
released version. But I haven't so far touched the management version of<br>
the EJB3 subsystem - in fact I had almost forgotten we had that. As a<br>
specific example, I introduced a "default-security-domain" management<br>
attribute for the EJB3 subsystem recently. Does this warrant a<br>
management version bump?<br>
<br>
[1] <a href="https://github.com/jbossas/jboss-as/pull/3175/files" target="_blank">https://github.com/jbossas/jboss-as/pull/3175/files</a><br>
[2] <a href="https://github.com/jbossas/jboss-as/pull/3197/files" target="_blank">https://github.com/jbossas/jboss-as/pull/3197/files</a><br>
<br>
-Jaikiran<br>
_______________________________________________<br>
jboss-as7-dev mailing list<br>
<a href="mailto:jboss-as7-dev@lists.jboss.org">jboss-as7-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jboss-as7-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jboss-as7-dev</a><br>
</blockquote></div><br>