[Pharo-dev] Catalog Entries

Sven Van Caekenberghe sven at stfx.eu
Tue Dec 18 07:52:18 EST 2018


So let us agree on the best name then, to minimise confusion going forward.

I am not sure I would go for camel case, git is typically lowercase (or so it feels), I agree 'release' should be part of the name, so

last-release
latest-release
lastRelease
latestRelease

What say you ?

> On 18 Dec 2018, at 13:45, Ben Coman <btc at openinworld.com> wrote:
> 
> 
> 
> On Tue, 18 Dec 2018 at 19:12, Sven Van Caekenberghe <sven at stfx.eu> wrote:
> I am trying to load https://github.com/svenvc/ztimestamp/releases/latest which is actually https://github.com/svenvc/ztimestamp/releases/tag/v24
> 
> The following works because that is the whole idea of releases (which are just tags)
> 
> Metacello new
>   baseline: 'ZTimestamp';
>   repository: 'github://svenvc/ztimestamp:v24';
>   load.
> 
> But I would like to do
> 
> Metacello new
>   baseline: 'ZTimestamp';
>   repository: 'github://svenvc/ztimestamp:latest';
> 
> This might be something good to have as a community convention,
> but "latest" on its own is a bit ambiguous.  Reading your subsequent post
> maybe "latestRelease"  would be good (or "lastRelease"), 
> to distinguish "latestStable" which is similar but not necessarily a release.
> 
> (or maybe I'm being too pedantic) 
> cheers -ben
> 
>   load.
> 
> Maybe that is not possible, maybe that has to be done in another way.
> 
> I know about master or other branch names, I was hoping latest was moving/tracking like  https://github.com/svenvc/ztimestamp/releases/latest does
> 
> > On 18 Dec 2018, at 12:05, Guillermo Polito <guillermopolito at gmail.com> wrote:
> > 
> > 
> > 
> > On Tue, Dec 18, 2018 at 12:00 PM Sven Van Caekenberghe <sven at stfx.eu> wrote:
> > 
> > 
> > > On 17 Dec 2018, at 20:18, Torsten Bergmann <astares at 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. 
> > 
> > I'm following the conversation in diagonal, but if this error is raised by metacello's iceberg integration it would mean that Tealight has no commitish (tag/branch) with the name latest.




More information about the Pharo-dev mailing list