<div dir="ltr"><div><div>We never said we are going to be renaming existing packages. <br></div>Especially because we don't want to break compatibly or make back porting harder.<br><br></div>What we did agree on is that new stuff should be in new package names. <br>
Old packages could be renamed only when the got some big upgrade/change that would break compatibility anyway.<br><br><div><div>--<br></div><div>tomaz<br></div><div><br><br><br></div></div></div><div class="gmail_extra"><br>
<br><div class="gmail_quote">On Thu, May 2, 2013 at 12:48 PM, Bill Burke <span dir="ltr"><<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Are you sure a package name change is a good idea? Won't it make it<br>
harder to pull/push changes upstream and downstream? And create<br>
additional work for those who already are the bottleneck in the release<br>
process? What does Fedora/RHEL do?<br>
<span class="HOEnZb"><font color="#888888">--<br>
Bill Burke<br>
JBoss, a division of Red Hat<br>
<a href="http://bill.burkecentral.com" target="_blank">http://bill.burkecentral.com</a><br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</font></span></blockquote></div><br></div>