> On 17 Dec 2018, at 20:18, Torsten Bergmann <astares@gmx.de> wrote:
>
> Model 1: Work with a single branch and close a release using a tag as version in git
> ===================================================================================
> This is I guess how Iceberg, Calypso and others are maintained now. You work on a specific (development) branch and
> use the git tagging to mark release like milestone of your project ("versions").
>
> This is the model I started to maintain ConfigurationOfTealight (which you will find in catalog
> and in https://github.com/astares/Tealight)
>
> So I tagged in git when I reached something shareable as you can see on the first releases: https://github.com/astares/Tealight/releases
> and then reference this git tagged version in my ConfigurationOfTealight:
>
> v0_0_4: spec
>�� �� �� ��<version: '0.0.4'>
>
>�� �� �� ��spec for: #'common' do: [
>�� �� �� �� �� �� �� ��spec blessing: #'stable'.
>�� �� �� �� �� �� �� ��spec
>�� �� �� �� �� �� �� �� �� �� �� ��baseline: 'Tealight' with: [
>�� �� �� �� �� �� �� �� �� �� �� �� �� �� �� ��spec
>�� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� ��className: 'BaselineOfTealight';
>�� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� �� ��repository: 'github://astares/Tealight:0.0.4/repository' ]]
>
>
> The advantage is that you use git to tag the releases, it is a reproducable stable version then and GitHub shows it on
> the "releases" tab. One typically can not modify the release afterwards (which is not 100% true as git tags could be moved but this is
> another story).
>
> So with this model you form and finalize/close a release by tagging in git/GitHub and reference it in your ConfigurationOf....
Would it not be possible to refer to the latest release ? For example:
> github://astares/Tealight:latest/repository
That way one would no longer have to update the ConfigurationOf (just like the BaselineOf does not have to be updated), just making a new release would be enough.
I tried, but I get Revspec 'latest' not found.