@JuliaRegistrator register v0.1.3

[jkhamphousone]

@JuliaRegistrator register

Patch release v0.1.3

As mentioned in #11 the solver is now Optimizer Agnostic! Currently supports GLPK and Gurobi

• Can not support SCIP, it doesn't support Lazy Constraints Callbacks
  • Solver remaining to test: CPLEX and Xpress

According to JuMP manual, the supported solver for Lazy Constraints Callbacks are:

• CPLEX, GLPK, Xpress, Gurobi

[JuliaRegistrator]

Error while trying to register: Version 0.1.2 already exists

[jkhamphousone]

@JuliaRegistrator register

Patch release v0.1.3

As mentioned in #11 the solver is now optimizer-agnostic! Currently supports GLPK and Gurobi

• Can not support SCIP, it doesn't support Lazy Constraints Callbacks
  • Solver remaining to test: CPLEX and Xpress
  • Adding Documenter.jl
  • JET tests are passing!

According to JuMP manual, the supported solver for Lazy Constraints Callbacks are:

• CPLEX, GLPK, Xpress, Gurobi

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/111227

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.3 -m "<description of version>" 91d972fec9e8b165677724df910b5919a3115586
git push origin v0.1.3

[jkhamphousone]

@JuliaRegistrator register

Releaste notes:

RingStarProblems v0.1.3 patch release

As mentioned in #11 the solver is now optimizer-agnostic! Currently supports GLPK and Gurobi

• Can not support SCIP, it doesn't support Lazy Constraints Callbacks
  • Solver remaining to test: CPLEX and Xpress
  • Adding Documenter.jl
  • JET tests are passing!

According to JuMP manual, the supported solver for Lazy Constraints Callbacks are:

• CPLEX, GLPK, Xpress, Gurobi

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/111227

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.3 -m "<description of version>" 6d121bb30b7686284b95ffd1fd968f29fd6f2f95
git push origin v0.1.3

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/111227

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.3 -m "<description of version>" 6d121bb30b7686284b95ffd1fd968f29fd6f2f95
git push origin v0.1.3

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/111227

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.3 -m "<description of version>" 6d121bb30b7686284b95ffd1fd968f29fd6f2f95
git push origin v0.1.3

[jkhamphousone]

@JuliaRegistrator register

Release notes:

Patch release v0.1.4

• Solving a small bug when calling rspoptimize

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/111232

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.4 -m "<description of version>" b67ecd338869244d21b00803209d4561527b9ce6
git push origin v0.1.4