4 Replies Latest reply on Apr 16, 2009 1:40 AM by Carlo de Wolf

    Revisiting versioning for components

    Carlo de Wolf Master

      Right now 'Fix Version' and 'Affects Version' reflects the version of ejb3-core which we are using. While this is the most accurate reflection of what we currently distribute via as-int, plugin and embedded, it bears no/little relationship to the version of that distribution.
      Which leads to weird tracking of:
      https://jira.jboss.org/jira/browse/EJBTHREE-1492
      https://jira.jboss.org/jira/browse/EJBTHREE-1803
      https://jira.jboss.org/jira/browse/EJBTHREE-1805

      So at least for the three distributed artifacts I think we should have versions:
      1. as-int
      2. embedded
      3. plugin

      This is then reflected and tracked on the road map.

      Hmm, still we have issues like:
      https://jira.jboss.org/jira/browse/EJBTHREE-1806

        • 1. Re: Revisiting versioning for components
          Carlo de Wolf Master

          We now also have the option on using 'Component Fix Version(s)'.

          • 2. Re: Revisiting versioning for components
            jaikiran pai Master

            I agree, the fix version right now isn't clear enough for tracking issues.


            Right now 'Fix Version' and 'Affects Version' reflects the version of ejb3-core which we are using.


            I thought it reflected the version of as-int


            So at least for the three distributed artifacts I think we should have versions:
            1. as-int
            2. embedded
            3. plugin


            Any specific reason, we want to limit it to these 3? Maybe because this is the only 3 ways (currently) that we distribute EJB3?


            We now also have the option on using 'Component Fix Version(s)'.

            So if a issue is reported against the "interceptors" component and fixed in 1.x.y version of the "interceptors" and the "interceptors" 1.x.y version is distributed through "as-int" version 1.a.b and "plugin" version 1.p.q, then we would mark it as:

            Component/s: interceptors
            Affects Version/s: None (what do we use here? the version of component or the distribution)
            Fix Version/s: 1.a.b, 1.p.q (Again how do we distinguish 1.a.b corresponds to as-int and 1.p.q to plugin)
            
            Component Fix Version(s): 1.x.y (this corresponds to interceptors version)


            • 3. Re: Revisiting versioning for components
              jaikiran pai Master

              Thinking a bit more, how about something like this:

              * Affects version will refer to distribution versions (like as-int, plugin, embedded) [1]
              * Fix version will refer to distribution versions (like as-int, plugin, embedded)
              * Component Affects Version - If some field like this could be made available, then we could use this to refer to each component's version. This field would in most of the cases be set by us and not usually by end users reporting the issue
              * Component Fix version - Refers to the component version

              [1] Still how do we distinguish 1.a.b version of as-int from 1.p.q version of plugin. Unless the versioning in JIRA is something like as-int-1.a.b and plugin-1.p.q

              • 4. Re: Revisiting versioning for components
                Carlo de Wolf Master

                Version distinction will be achieved by having embedded-x.y and plugin-x.y.

                Fix version can't be set on an component update, because you can't be sure that the component will make it into that specific release.