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

Move to JuliaMolSim #53

Closed
cortner opened this issue Nov 7, 2019 · 11 comments
Closed

Move to JuliaMolSim #53

cortner opened this issue Nov 7, 2019 · 11 comments

Comments

@cortner
Copy link
Member

cortner commented Nov 7, 2019

Any chance I can convince you to move over to JuliaMolSim and register the package in the MolSim registry? Once we start using it, it would be very helpful to have some minimal versioning information. Even without any expectation of backward compatibility - I generally refuse to guarantee that.

@cortner
Copy link
Member Author

cortner commented Nov 7, 2019

I'm happy to help with any package manager / registry issues you might have...

@antoine-levitt
Copy link
Member

We're going to move over to JuliaMolSim. Was the transition painful? Did you just tell people to change their git remote?

Re the registry, we're a bit reluctant to do a release now - we want to clean things up and make a proper release, but it'll probably take another month or so. But if you just need a tag then we can probably do that? (I'm not very familiar with how that works...)

@cortner
Copy link
Member Author

cortner commented Nov 8, 2019

As long as you don’t register a release there is nothing to do really - github just forwards the links

@cortner
Copy link
Member Author

cortner commented Nov 8, 2019

Re registry- sure sounds sensible. But reconsider it. I used to be extremely reluctant as well. But the point of having a separate registry means we don’t have to follow very high standards. In fact you can register your package in both MolSim and General and have only high quality releases in General. Also the point of semver is to lower the barrier to creating new releases as frequently as necessary.

@cortner
Copy link
Member Author

cortner commented Nov 8, 2019

Actually moving the repo is a 23s process.

@mfherbst
Copy link
Member

mfherbst commented Nov 8, 2019

@cortner One more thing: Before the move, could you just reassure I have sufficient permissions to quickly set up the attached services (Travis, coveralls etc.) at the organisation level ... I recall from a different project, that github's permission system is quite a bit more involved compared to single repos and I do not want to get locked out 😄.

@mfherbst
Copy link
Member

mfherbst commented Nov 8, 2019

Oh and regarding the release ... we agreed to release a 0.0.1 to MolSim next week, so you got us convinced @cortner 😄.

@cortner
Copy link
Member Author

cortner commented Nov 8, 2019

I can just give you admin access - Antoine already has that as well.

@cortner
Copy link
Member Author

cortner commented Nov 8, 2019

Re release: once you start using your code for projects rather than as a project for its own sake you will really see the benefit! And just feel free to make 0.0.x increments arbitrarily breaking.

@mfherbst
Copy link
Member

mfherbst commented Nov 8, 2019

Perfect thanks very much ... I'll try to get it on asap.

@mfherbst
Copy link
Member

Done now.

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

No branches or pull requests

3 participants