seaside.gemstone.com is not forwarding to seaside.gemtalksystems.com

[dalehenrich]

@pdebruic updated the gs_master branch, but each of these tagged releases need to be updated (since one or more of them are referenced from ConfigurationOfSeaside3):

• https://github.com/GsDevKit/Seaside31/releases/tag/v3.1.2-gs
• https://github.com/GsDevKit/Seaside31/releases/tag/v3.1.3-gs
• https://github.com/GsDevKit/Seaside31/releases/tag/v3.1.3.1-gs

[dalehenrich]

Used Paul's commit as the new commit for 3.1.3.1

[dalehenrich]

Do we need to update these as well?:

• https://github.com/GsDevKit/Seaside31/releases/tag/v3.1.2.1-gs
• https://github.com/GsDevKit/Seaside31/releases/tag/3.1.1.3-gs31

[dalehenrich]

looks like we should update the following branches/tags, since they are referenced from ConfigurationOfSeaside3 as well:

• github://glassdb/Seaside31:gemstone3.1/repository
• github://glassdb/Seaside31:3.1.1-gs31/repository
• github://glassdb/Seaside31:3.1.1.3-gs31/repository
• github://GsDevKit/Seaside31:v3.1.2.1-gs/repository

so that'd be yes to the two above as well:

• https://github.com/GsDevKit/Seaside31/releases/tag/v3.1.2.1-gs
• https://github.com/GsDevKit/Seaside31/releases/tag/3.1.1.3-gs31

[dalehenrich]

tag v3.1.3-gs test failed, but not from load errors so we're cool ... tagged

[dalehenrich]

tag v3.1.2-gs test failed but not from load errors (same as v3.1.3-gs test failures) ... tag it and bag it

[dalehenrich]

branch gs_master_3.1.2.1 tests failed but not from load errors (same as v3.1.3-gs test failures) ... tag it and bag it

[dalehenrich]

branch gs_master_3.1.1.3 has a build issue. It's not directly related to seaside.gemstone.com (yet), but the load has not completed successfully...

[dalehenrich]

And this morning, seaside.gemstone.com is again being forwarded to seaside.gemtalksystems.com, so I will close this bug without retagging 3.1.1.3 or retagging the glassdb releases ...