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

[Dev] New package #45

Closed
ocots opened this issue Sep 10, 2024 · 3 comments
Closed

[Dev] New package #45

ocots opened this issue Sep 10, 2024 · 3 comments
Assignees
Labels
internal dev Modification to the code is requested and should not affect user experiment

Comments

@ocots
Copy link
Member

ocots commented Sep 10, 2024

@frapac @jbcaillau @PierreMartinon

What do you think we need to do before trying to register OptimalControlProblems.jl into the General Julia registry?

@ocots ocots added the internal dev Modification to the code is requested and should not affect user experiment label Sep 10, 2024
@ocots ocots self-assigned this Sep 10, 2024
@jbcaillau
Copy link
Member

@ocots go!

NB. @0Yassine0 would be nice to use the new syntax ocp = @def ... (instead of @def ocp ...)

@ocots
Copy link
Member Author

ocots commented Sep 13, 2024

@JuliaRegistrator register

@JuliaRegistrator
Copy link

Registration pull request created: JuliaRegistries/General/115146

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.1 -m "<description of version>" e28285cb58c3a56e70584679b8468bf40125509f
git push origin v0.1.1

Also, note the warning: This looks like a new registration that registers version 0.1.1.
Ideally, you should register an initial release with 0.0.1, 0.1.0 or 1.0.0 version numbers
This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

@ocots ocots closed this as completed Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal dev Modification to the code is requested and should not affect user experiment
Projects
None yet
Development

No branches or pull requests

3 participants