New package: LSL v0.1.0

[JuliaRegistrator]

• Registering package: LSL
• Repository: https://github.com/samuelpowell/LSL.jl
• Created by: @samuelpowell
• Version: v0.1.0
• Commit: 2af3d560b3f1157f1fb8a1448c9c4ddd71814395
• Reviewed by: @samuelpowell
• Reference: Register v0.1.0 samuelpowell/LSL.jl#9 (comment)

[fredrikekre]

Can you retrigger to resolve the conflict? Also, how about calling this LabStreamingLayer (LabStreamingLayers?)

Edit: nvm, this was wrapping a lsl library.

[samuelpowell]

@fredrikekre retriggered. And yes, this wraps a library called lsl, which has various language bindings which use this naming format.

[ghost]

Your new package pull request does not meet all of the guidelines for automatic merging.

Specifically, your pull request does not meet the following guidelines:

• Name does not meet all of the following: starts with a capital letter, ASCII alphanumerics only, ends in lowercase
• Name is not at least five characters long
• The following dependencies do not have a compat entry that has an upper bound: CEnum, BinaryProvider, LightXML

---

It is important to note that if your pull request does not meet the guidelines for automatic merging, this does not mean that your pull request will never be merged. It just means that your pull request will require manual review by a human.

These guidelines are intended not as requirements for packages but as very conservative guidelines, which, if your new package or new version of a package meets them, it may be automatically merged.

---

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.

Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)

If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

---

[noblock]

[ghost]

Your new package pull request does not meet all of the guidelines for automatic merging.

Specifically, your pull request does not meet the following guidelines:

• Name does not meet all of the following: starts with a capital letter, ASCII alphanumerics only, ends in lowercase
• Name is not at least five characters long

If you want to prevent this pull request from being auto-merged, simply leave a comment.

(If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.)

---

It is important to note that if your pull request does not meet the guidelines for automatic merging, this does not mean that your pull request will never be merged. It just means that your pull request will require manual review by a human.

These guidelines are intended not as requirements for packages but as very conservative guidelines, which, if your new package or new version of a package meets them, it may be automatically merged.

---

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.

Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)

If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

---

[noblock]

[samuelpowell]

@fredrikekre I have addressed your comments and those of zeptodoctor, this should be good to merge now.

[ghost]

Your new package pull request does not meet all of the guidelines for automatic merging.

Specifically, your pull request does not meet the following guidelines:

• Name does not meet all of the following: starts with a capital letter, ASCII alphanumerics only, ends in lowercase
• Name is not at least five characters long

If you want to prevent this pull request from being auto-merged, simply leave a comment.

(If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.)

---

It is important to note that if your pull request does not meet the guidelines for automatic merging, this does not mean that your pull request will never be merged. It just means that your pull request will require manual review by a human.

These guidelines are intended not as requirements for packages but as very conservative guidelines, which, if your new package or new version of a package meets them, it may be automatically merged.

---

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.

Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)

If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

---

[noblock]

[julia-tagbot]

I've created release v0.1.0, here it is.