Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GemStone should use master branch of GsDevKit_home #72

Closed
dalehenrich opened this issue Feb 25, 2016 · 3 comments
Closed

GemStone should use master branch of GsDevKit_home #72

dalehenrich opened this issue Feb 25, 2016 · 3 comments
Assignees
Labels

Comments

@dalehenrich
Copy link
Collaborator

For PR #51, changes were required to GsDevKit_home and those changes were made on the dev branch. Now that the PR #51 work is done, I will merge the needed changes into the master branch with GsDevKit/GsDevKit_home#75 and once that's done, I will need to switch back to using the master branch of GsDevKit_home ...

dalehenrich added a commit to dalehenrich/smalltalkCI that referenced this issue Feb 25, 2016
@fniephaus
Copy link
Member

I think this relates to #54, right? And why would I want to switch the branch?

@dalehenrich
Copy link
Collaborator Author

Yes, and I may not fix Issue #54 right now ...

I will want to switch the branch of GsDevKit_home that is being used if there is a bugfix in a branch that needs to be tested (as was the case here --- smalltalkCI green tests were dependent upon using the dev branch of GsDevKit_home, until the code in the dev branch could be merged to master ...

IN the general case, this well extend to specifying a different GsDevKit_home fork to be used with smalltalkCI ...

And of course I have yet to figure out how I will test GsDevKitHome itself using smalltalkCI, but it will involve "changing the version of GsDevKit_home that is being used to bootstrap things"

@fniephaus
Copy link
Member

f0fcfbb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants