4.6 Codename (was: Squeak 4.6 Release Notes)

>    except that Spur is nothing to do with 4.6, so "Spur" in the title is wrong,

Ah, I figured that would need some explaining.  The word "Spur" on
that page refers to the codename of this release.  The last time we
had a discussion about codenaming this release, we had a smattering of
ideas and not much consensus.  So, I just went with "Spur" for that
moment to get on with the notes until that could be solved.

Then, it hit me, if we DIDN'T come up with a codename for this
software release then how would we meaningfully refer to it besides
the number 4.6?  I believe we would say, "that was the release when we
made the image ready for Spur", which, in further discussion would
naturally contract to "the Spur release" for communication efficiency.

I know that Spur is the name of your VM software, but does that mean
it cannot also be the name of this release?  I think it fits but if
you object I did think of another good one I like...

> and become: is not faster, and ObjectHistory still works.

That was pulled straight from the notes of one of the versions.  I'll
move it to the 5.0 page.

>  We need a separate page for 5.0,

Yes, we are doing two releases now, one thing at a time please.

> which /is/ Spur; it has all the improvements in 4.6, except for ObjectHistory being unsupported,
> but is faster, with much faster become: and improved GC.

Okay, my plan is for the 5.0 page to _just_ be those items, which is
perfect.  And since it is the same image contents I thought both 4.6
and 5.0 could be codenamed "Spur" but, if that rubs you the wrong way
I have another name picked for 4.6 which I like almost as much.

Let me know..

> I know that Spur is the name of your VM software, but does that mean
> it cannot also be the name of this release?  I think it fits but if
> you object I did think of another good one I like...
>

It will certainly create a confusion, that this release is based on  
Spur. I would be confused! Please, don't do that.

On 21.05.2015, at 18:08, Mateusz Grotek <[hidden email]> wrote:

>> I know that Spur is the name of your VM software, but does that mean
>> it cannot also be the name of this release?  I think it fits but if
>> you object I did think of another good one I like...
>
> It will certainly create a confusion, that this release is based on Spur. I would be confused! Please, don't do that.

+1. There's already confusion of what Spur actually is.
I have heard people saying it's a new VM (as in 'This is a Cog VM, this is Spur),
or just image format (as in 'Why is there problems with Characters? its only a new image format'),
or just object format (as in 'Why can't the interpreter load Spur images and just ignore the Character stuff?').


Best regards
        -Tobias

On 21-05-2015, at 10:21 AM, Tobias Pape <[hidden email]> wrote:

How about
"This is a dual release; 4.6 continues the 4.5 system with many improvements, whilst 5.0 introduces the Spur memory model and the new VM required to support it. Aside from differences related to making Characters immediates (as with SmallIntegers) the two systems appear the same to programmers"


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Useful random insult:- All foam, no beer.

On 5/21/15, tim Rowledge <[hidden email]> wrote:
Seems to be like the nucleus of a message which is the base for a
communication strategy about the release.

--Hannes

>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> Useful random insult:- All foam, no beer.
>
>
>
>

I thought about that but then decided we have an opportunity to
exercise our release process twice, once for 4.6 and once for 5.0.
Treat each relase separately and if we pay attenion to our release
process maybe we'll even get to understand and refine it a little.

First lets finish up everything for 4.6 including even the news
announcement.  The announcement should not mention Spur.  Then
immediately repeat our process for 5.0.  Then put out another news
release about 5.0 the following week.

We don't often get this chance to, as Chris Rock would say, "go pop
Pop POP!!" from a marketing perspective.  This is one.  :)

On Thu, May 21, 2015 at 12:51 PM, tim Rowledge <[hidden email]> wrote:

On 5/23/15, Chris Muller <[hidden email]> wrote:
+1

> We don't often get this chance to, as Chris Rock would say, "go pop

I meant Chris Tucker, of course, not Chris Rock..

https://www.youtube.com/watch?v=5goH0hxUM8A

Hi, there! :)

-1 for Stirrup
-1 for Spur

What about colors?
http://www.colourlovers.com/web/blog/2008/04/22/all-120-crayon-names-color-codes-and-fun-facts

"Mountain Meadow" representing the solid code base in Squeak 4.6.
"Sky Blue" referring to the new image format and hence future (sight/direction/view) of Squeak resp. Squeak 5.0.

Many people might not get technical metaphors anyway. :D

Just my two cents. ;)

Best,
Marcel

I agree with Tobias that naming a release "Spur" could create confusion. However, I'm not good with names anyway and always refer to any release by its number.

They are not my favorite names either but they reasonably fit -- the
"Stirrup" will get you into the saddle, "Spurs" to make it go..   :-/

Codenames are relatively unimportant, so rather than burn any more
time and energy talking about them lets just go with this and move
forward.

On Tue, May 26, 2015 at 2:54 AM, marcel.taeumel <[hidden email]> wrote:

Or just don't use a codename this time... ;-)

Best,
Marcel

Hi,

On 26.05.2015, at 09:54, marcel.taeumel <[hidden email]> wrote:

> -1 for Stirrup
> -1 for Spur


I have the same feeling about this code names.
Especially the overlap of Spur and Spur does not
sound right to me. Marcel's idea of colors is
fun.
  Side note: I find the code names for pypy quite
amusing [1]. Maybe we can draw inspiration there?
They are not technology related, which I find
a good thing.


Best regards
        -Tobias

[1]: https://pypy.readthedocs.org/en/latest/index-of-release-notes.html

I agree.

Best,
Robert

---
www.hirschfeld.org