Register package

Question

Register package

Opened this issue 2 years ago · 53 comments

Answer 1 · 2022-04-28T16:50:59.000Z

Registration pull request created: JuliaRegistries/General/59309

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.0 -m "<description of version>" e5999400f03fae7f78c6b7a9971fcbf534d4c0d2
git push origin v0.1.0

Answer 2 · 2022-06-04T13:13:35.000Z

@JuliaRegistrator register

Answer 3 · 2022-06-04T13:13:46.000Z

Registration pull request created: JuliaRegistries/General/61727

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>" d47cdd371a8137605e7c5f5744d2fbe930ae5d7d
git push origin v0.1.1

Answer 4 · 2022-06-05T15:29:56.000Z

@JuliaRegistrator register

Answer 5 · 2022-06-05T15:30:04.000Z

Registration pull request updated: JuliaRegistries/General/61727

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>" 8729dd895b1e36e427efa92df64509fa547f0797
git push origin v0.1.1

Answer 6 · 2022-06-05T21:17:04.000Z

@JuliaRegistrator register

Answer 7 · 2022-06-05T21:17:10.000Z

Registration pull request updated: JuliaRegistries/General/61727

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>" 51b1bf3303aac490cc8e0d2a97764c7b399fdb11
git push origin v0.1.1

Answer 8 · 2022-06-10T13:43:28.000Z

@JuliaRegistrator register

Answer 9 · 2022-06-10T13:43:38.000Z

Registration pull request created: JuliaRegistries/General/62123

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.2 -m "<description of version>" 6f36e4c48b18a881ca3b0cbfbba6c2ac42e214a1
git push origin v0.1.2

Answer 10 · 2022-06-10T14:02:49.000Z

@JuliaRegistrator register

Answer 11 · 2022-06-10T14:02:56.000Z

Registration pull request updated: JuliaRegistries/General/62123

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.2 -m "<description of version>" c728e5a4790bab639c4e9cafe756ea626f342661
git push origin v0.1.2

Answer 12 · 2022-06-10T16:36:55.000Z

@JuliaRegistrator register

Answer 13 · 2022-06-10T16:38:24.000Z

Registration pull request updated: JuliaRegistries/General/62123

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.2 -m "<description of version>" 599a46dd728ac3e03a4b6b3e30eaf050dfc2edd6
git push origin v0.1.2

Answer 14 · 2022-06-11T20:32:24.000Z

@JuliaRegistrator register

Answer 15 · 2022-06-11T20:32:26.000Z

Error while trying to register: "Tag with name v0.1.2 already exists and points to a different commit"

Answer 16 · 2022-06-11T20:33:31.000Z

@JuliaRegistrator register

Answer 17 · 2022-06-11T20:33:38.000Z

Registration pull request created: JuliaRegistries/General/62208

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>" 26e8b5f8db8907da40e56a36294de44c11f5c9d9
git push origin v0.1.3

Answer 18 · 2022-06-19T11:48:38.000Z

@JuliaRegistrator register

Answer 19 · 2022-06-19T11:48:47.000Z

Registration pull request created: JuliaRegistries/General/62640

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>" b48e92f96e065dd0e8fe5bb5df234153513cf84f
git push origin v0.1.4

Answer 20 · 2022-06-23T23:25:33.000Z

@JuliaRegistrator register

Answer 21 · 2022-06-23T23:25:42.000Z

Registration pull request created: JuliaRegistries/General/62978

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.5 -m "<description of version>" d9dd6102593d94334e93e6ba910d322d25e86112
git push origin v0.1.5

Answer 22 · 2022-06-25T21:56:38.000Z

@JuliaRegistrator register

Answer 23 · 2022-06-25T21:56:48.000Z

Registration pull request created: JuliaRegistries/General/63111

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.6 -m "<description of version>" 83767b5f7e4b95297ffe317dcf6409ca4b81748d
git push origin v0.1.6

Answer 24 · 2022-07-03T06:35:52.000Z

@JuliaRegistrator register

Answer 25 · 2022-07-03T06:36:01.000Z

Registration pull request created: JuliaRegistries/General/63561

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.7 -m "<description of version>" 908f4d8d10768579e80d6157107bf4215195c51d
git push origin v0.1.7

Answer 26 · 2024-03-17T21:56:04.000Z

@JuliaRegistrator register

Answer 27 · 2024-03-17T21:56:18.000Z

Registration pull request created: JuliaRegistries/General/103055

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.2.0 -m "<description of version>" 48972773029cce00e925ce6a93e8024b5b73fbeb
git push origin v0.2.0

Answer 28 · 2024-03-19T13:14:40.000Z

@JuliaRegistrator register

Answer 29 · 2024-03-19T13:14:48.000Z

Error while trying to register: Version 0.2.0 already exists

Answer 30 · 2024-03-29T14:00:24.000Z

@JuliaRegistrator register

Answer 31 · 2024-03-29T14:00:37.000Z

Registration pull request created: JuliaRegistries/General/103864

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.2.1 -m "<description of version>" 5ecb7747acceb2a1388586fb0ecc8342ca6d1700
git push origin v0.2.1

Answer 32 · 2024-03-31T14:44:58.000Z

@JuliaRegistrator register

Release notes:

Breaking changes

the log file format changed, old log files cannot be opened with this version
the number of segments is added as meta data to the log files
five variables have been added to the SystemState that can be freely used, their names can be added as meta data to the log file

New Features

the example autopilot.jl was vastly improved
a menu with 6 pre-defined plots was added to the GUI
a statistics dialog was added
saving and loading of log files added
a second menu was added that allows to change the tolerance of the solver

Answer 33 · 2024-03-31T14:45:05.000Z

Error while trying to register: Version 0.2.1 already exists

Answer 34 · 2024-04-03T15:11:56.000Z

@JuliaRegistrator register

Release notes:

Breaking changes

the log file format changed, old log files cannot be opened with this version
the number of segments is added as meta data to the log files
five variables have been added to the SystemState that can be freely used, their names can be added as meta data to the log file

New Features

the example autopilot.jl was vastly improved
a menu with 6 pre-defined plots was added to the GUI
a statistics dialog was added
saving and loading of log files added
a second menu was added that allows to change the tolerance of the solver
the new, pure Julia solver DFBDF is now the default. It is in average 4 times faster, uses only half the memory and is much more stable

Answer 35 · 2024-04-03T15:12:07.000Z

Registration pull request created: JuliaRegistries/General/104155

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.2.2 -m "<description of version>" 2f52ab997f6f9911a8fa97558475dc58f0c75397
git push origin v0.2.2

Answer 36 · 2024-04-03T15:14:51.000Z

Registration pull request updated: JuliaRegistries/General/104155

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.2.2 -m "<description of version>" 2f52ab997f6f9911a8fa97558475dc58f0c75397
git push origin v0.2.2

Answer 37 · 2024-05-06T15:21:29.000Z

@JuliaRegistrator register

Release notes:

Changed

use 60 Hz refresh rate for 3x, 6x, 9x and 12x time lapse
refactoring: add type KiteApp to the script autopilot.jl
make use of log_level settings, print a lot less for log_level=0
refactoring: split flightpathplanner.jl in flightpathplanner.jl and flightpathcalculator.jl
created the simplified components flightpathplanner2.jl and flightpathcalculator2.jl;
they are easier to understand and contain a lot less hard-coded constants

Added

adapt time_lapse according to menu selection
adapt text_mod such that the text update rate stays constant
make it possible to change t_sim using the GUI
add the plots plot_elev_az2 and plot_side_view2 that omit the first power cycle
add the plots plot_elev_az3, plot_side_view3 and plot_front_view3 that omit the first two power cycles
add the plot aerodynamics that plots the lift-over-drag of the kite
add time series of fig8 to plot_control
add the file kiteobservers.jl which provides the type KiteObserver and methods to
determine deviations from the desired flight path
add the script learning.jl that provides the method train() that implements iterative learning
of a vector of flight path corrections

Answer 38 · 2024-05-06T15:21:43.000Z

Registration pull request created: JuliaRegistries/General/106262

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.2.3 -m "<description of version>" 8e16738aa9335d238a2c6950e3354bbc8363fd96
git push origin v0.2.3

Answer 39 · 2024-05-06T16:00:00.000Z

@JuliaRegistrator register

Answer 40 · 2024-05-06T16:00:13.000Z

Registration pull request updated: JuliaRegistries/General/106262

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.2.3 -m "<description of version>" 06bb1c07c5e019b0abfaba3e55d74b48ceb9c2cc
git push origin v0.2.3

Answer 41 · 2024-06-18T17:14:43.000Z

@JuliaRegistrator register

Release notes:

Changed

add the field corr_vec to all fpp_settings_xxx.yaml files
modify kiteobserver.jl to use this correction vector
the projects hydra10_951 and hydra20_600 hydra20_920 work correctly now; key change: set k_c2_high to 6.0
new plot control_plot_II
remove compatibility with Julia 1.9, version 1.10 is the only supported version now

Answer 42 · 2024-06-18T17:14:56.000Z

Registration pull request created: JuliaRegistries/General/109281

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.2.4 -m "<description of version>" ad68d98043cc3335a18b9351556be939c8451b3c
git push origin v0.2.4

Answer 43 · 2024-06-26T14:06:09.000Z

@JuliaRegistrator register

Release notes:

KiteControllers v0.2.5 - 2024-06-26

Added

copyright disclaimer from TU Delft

Changed

fix #35, save the default log file in the output folder

Answer 44 · 2024-06-26T14:06:25.000Z

Registration pull request created: JuliaRegistries/General/109815

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.2.5 -m "<description of version>" 31cb82bfb9c92626879ee8c380a70975d1ca406e
git push origin v0.2.5

Answer 45 · 2024-07-02T08:07:57.000Z

@JuliaRegistrator register

Release notes:

Changed

downgrade GLFW_jll to fix an issue on Ubuntu 24.04 and on Mac

Added

add section kps4-3l to all settings files to be compatible with latest KiteUtils package

Answer 46 · 2024-07-02T08:08:10.000Z

Registration pull request created: JuliaRegistries/General/110197

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.2.6 -m "<description of version>" ecc38376acd926c0f27d88778b7703a3e400503d
git push origin v0.2.6

Answer 47 · 2024-07-12T16:43:06.000Z

@JuliaRegistrator register

Release notes:

Fixed

fix control_plot on Windows (added sleep)
fix cycle counting in FPP

Added

add function plot_timing2()
add lower limit for C2 of 2.0

Answer 48 · 2024-07-12T16:43:17.000Z

Registration pull request created: JuliaRegistries/General/110964

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.2.7 -m "<description of version>" edb9b6af486393afb56a021af03eaea56dc59f7c
git push origin v0.2.7

Answer 49 · 2024-07-28T17:42:38.000Z

@JuliaRegistrator register

Release notes:

Changed

bump KiteUtils to 0.7.2
bump WinchModels to 0.3.2
bump KiteViewers to 0.4.16
adapt WinchController to new WinchModel interface
fix tests

Answer 50 · 2024-07-28T17:42:51.000Z

Registration pull request created: JuliaRegistries/General/111934

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.2.8 -m "<description of version>" 8a1e1de78c43131f777fd9bb5dc7d9e2bbc0bb45
git push origin v0.2.8

Answer 51 · 2024-07-28T17:43:56.000Z

Registration pull request updated: JuliaRegistries/General/111934

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.2.8 -m "<description of version>" 8a1e1de78c43131f777fd9bb5dc7d9e2bbc0bb45
git push origin v0.2.8

Answer 52 · 2024-08-07T10:24:49.000Z

@JuliaRegistrator register

Release notes:

Changed

bump KiteUtils to 0.7.4
bump KiteModels to 0.6.3
fix some examples and the script create_sys_image
explain different installation methods in README.md

Answer 53 · 2024-08-07T10:25:03.000Z

Registration pull request created: JuliaRegistries/General/112564

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.2.9 -m "<description of version>" 0b00d73ca097965eabc61f209eace7913e7a396d
git push origin v0.2.9