Yes, major version bump please. This makes it straightforward to avoid
version conflicts with EAP 6.x. If EAP 6.x needs to change API in more
than a bug fix way, they can use a minor version with no fear that
community AS has already used that # for something else.

On 2/25/13 7:11 AM, Tomaž Cerar wrote:
> Hi,
>
> I remember few discussions on IRC in last weeks(s) about how to handle
> version bumps for subsystem model when changes are done on AS8 codebase.
>
> It was somewhat agreed that instead of bumping minor version we should
> upgrade major version.
>
> aka instead of doing 1.2 --> 1.3, new version should be 2.0
>
> That gives us flexibility of bumping minor version to 7.x codebase if
> need arises.
>
> I am writing this as there was some PRs lately that bump just minor version.
>
> So, can we get an agreement of new versioning rules, that we will then
> follow.
>
> I personalty favor major version bumps...
>
>
> --
> tomaz
>
>
>
>
>

> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>


--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev