[Squeak5.2rc1][ReleaseActivity] SqueakMap entries: Please make sure you have checked the 'published' flag!

Hello

The discussion about SqueakMap entries (see most recent email by Chris
Muller)  has shown that the following is important:

   You MUST check the 'published' flag in the entry.

Otherwise the client code will load an older version thus not giving
the users the release you intend them to give.

Regards
Hannes

Thanks for the clarity Hannes.  Here are some finer points to note about this:

  - This is nothing new, it's been this way forever.

  - It only affects when installing at the package level, not the
release level which is the normal use case.

  - If there is only one release for a particular Squeak version (the
usual case), then there is only one correct version to load, even
though the Warning is annoying and/or disruptive.

  - checking the 'published' box will make it so the Warning is not
displayed during the above conditions

I think we now have a clearer understanding of the potential use for
the "published" flag -- what you said Hannes -- for the case when
there is more than one release per Squeak release, although I suppose
it should probably pick the most recent then...   Hmm...
On Mon, Oct 8, 2018 at 3:18 PM H. Hirzel <[hidden email]> wrote:

On 10/8/18, Chris Muller <[hidden email]> wrote:
> Thanks for the clarity Hannes.  Here are some finer points to note about
> this:

And thank you for the additional notes. This helps us to move on.
This is a 're-learning exercise' for us.

>   - This is nothing new, it's been this way forever.

       Good point. Unfortunately people seem to have forgotten about this.....


>   - It only affects when installing at the package level, not the
> release level which is the normal use case.

      This is a finer point I do not understand. My tests in the
recent days did not give a good experience.


>   - If there is only one release for a particular Squeak version (the
> usual case), then there is only one correct version to load, even
> though the Warning is annoying and/or disruptive.

       annoying and disruptive are the right words for this.
       I get the impression that something is highly unfinished and/or
that I am doing
       something wrong for something which should be easy.

       We are talking about 'one-click' installation after old.

       The alternative is to search around on the internet for various
kinds of releases in
       maybe different repositories and to figure out which one might
be the one which
       has been tested for 5.2 and executing installation scripts.

>   - checking the 'published' box will make it so the Warning is not
> displayed during the above conditions

       Yes.

> I think we now have a clearer understanding of the potentiause for
> the "published" flag -- what you said Hannes -- for the case when
> there is more than one release per Squeak release, although I suppose
> it should probably pick the most recent then...   Hmm...

Yes, this  was our 're-learning exercise'. To share the experience for
the next time some notes in the help system at a prominent place seem
to be a solution. I'll think about it and try to come up with a note
in the inbox tomorrow ...

--Hannes

On Mon, Oct 08, 2018 at 03:30:56PM -0500, Chris Muller wrote:
I think that it already does pick the most recent release in that case:

   lastPublishedReleaseForCurrentSystemVersion
      "Return the latest published release marked
      as compatible with the current SystemVersion."

So I expcet that SMLoader-cmm.92 in the inbox is going to do exactly
what we want :-)

Dave