Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-dev] version management

Hi,


On Wed, Mar 26, 2014 at 5:47 PM, Steffen Pingel
<steffen.pingel@xxxxxxxxxxx> wrote:
> Hi,
>
> we have had a bit of confusion around the process for managing versions in
> the last release. Up to now we have managed all versions using a script
> that, depending on the planned release type, simply updates
> major/minor/service revision for all bundles and features (including poms
> etc.).
>
> We usually ran the script shortly after creating the release branch so
> development in master could continue for the next release and updated
> versions in all projects in one go.
>
> This isn't exactly by the book since we end up changing versions for bundles
> and features that may not have change in the release and we sometimes update
> the minor versions for bundles that don't have new API (which would only
> warrant an update of the service revision).
>
> We chose that process for its simplicity for developers (and consumers)
> since we didn't have good tooling available manage versions, particularly to
> easily detect when (service) revisions needed to be updated. The CDO project
> has filled that gap recently [1] but I have only briefly tested the
> workspace integration and I'm not sure if we could integrate version
> validation with Tycho.
>
> I just wanted to hear if anyone has thoughts on recommendations for managing
> versions?

As a consumer, it would prefer that exported package versions would
only be based on the API evolution ( or lack thereof ). In practice, I
import the mylyn APIs with the same major version component, e.g.
[3.6.0,4.0.0), so my only wish would be that exported versions don't
get changed for marketing reasons. For instance, if Mylyn 4.0 is a
major release feature-wise, but does not break API, please don't
export the packages with version 4.0.0  .

Thanks,

Robert

>
> There is also a question whether versions should be managed across the
> entire code base as part of releases or if there are components that should
> be excluded and managed separately?
>
> Steffen
>
>
> [1]
> https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg10419.html
>
> --
> Steffen Pingel
> Principal Software Engineer, Eclipse Mylyn
> Mylyn Tasks Lead
> http://tasktop.com
>
> _______________________________________________
> mylyn-dev mailing list
> mylyn-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-dev
>



-- 
http://robert.muntea.nu/


Back to the top