@dalehenrich the merge conflict points to differences in the packaging I made here: SeasideSt@9d4fe1a

This was done to ease maintenance, since the 'filename' difference was off-putting tools in Tode. I will fix the baseline with that in mind and if you are happy, you can hit the merge button ;-)

Okay rerunning GsDevKit_home tests using SeasideSt/Grease to validate most recent changes

Looks like the thisContext test is failing for 2.4.x. I don't think that it is really necessary to support 2.4.x moving forward ... so removing it from the travis lineup would not be a crime :)

Haha, indeed. I will just remove that version from the test lineup.
Getting back to this asap ;-)

Haha, and the travis build is still running, but it seems to be passing, so it's looking good ... when travis finishes I will want to manually do a reload from the old version to the new version to see if there are any hiccups (actually I can do this at any time and will when I find the time) ...

... oh, my browser hadn't updated ... rerunning the one test that failed ...

@dalehenrich I added your lineup of gs3.7 to 3.9 to the baseline (future proofness? :-) ). The difference now, besides indentation, is about the last statement:

	spec
		for:
			#(#'gs3.2.x' #'gs3.3.x' #'gs3.4.x' #'gs3.5.x' #'gs3.6.x' #'gs3.7.x' #'gs3.8.x' #'gs3.9.x')
		do: [ 
			spec
				package: 'Grease-Tests-GemStone-Core'
				with: [ spec file: 'Grease-Tests-GemStone-Core.v32' ] ]

vs

spec
    for: #(#'gs3.2.x' #'gs3.3.x' #'gs3.4.x' #'gs3.5.x' #'gs3.6.x')
    do: [ 
      spec
        package: 'Grease-Tests-GemStone32-Core'
		    with:[ spec requires: 'Grease-Tests-Core' ];
		  package: 'Grease-Tests-Core'
        	 with: [ spec includes: 'Grease-Tests-GemStone32-Core' ] ]

This is the change I referred to earlier.

Unless you see issues with that, I will just push the baseline of SeasideSt/Grease

I guess, I can't tell quite what you are doing ... Removing the package 'Grease-Tests-GemStone32-Core'? ... If things are working correctly then I suppose it is cool :)

I added it :)
It used to be done with that ‘file:’ message.

I just did a test load of SeasideSt/Grease:gsdevkit-merge into a 3.6.0 stone with GsDevKit/Grease:master loaded and it loaded without error (yeah!), when I looked at baselineGemStone: , I saw the following:

	spec
		for:
			#(#'gs3.2.x' #'gs3.3.x' #'gs3.4.x' #'gs3.5.x' #'gs3.6.x' #'gs3.7.x' #'gs3.8.x' #'gs3.9.x')
		do: [ 
			spec
				package: 'Grease-Tests-GemStone32-Core'
					with: [ spec requires: 'Grease-Tests-Core' ];
				package: 'Grease-Tests-Core'
					with: [ spec includes: 'Grease-Tests-GemStone32-Core' ] ]

Other than the fact that I thought that you had done the opposite :)

I ran the tests and they are all green, so merge away ...