David P. Baker

**Current decision**: Because we are not planing to support annotation implication in 1.0 (#35, #307), this issue is not relevant for 1.0. **Proposal for 1.0: Finalize the current decision.** If...

I think `org.jspecify:jspecify` is a fine name for the annotations artifact, better than `:annotations` for the reasons discussed. I could see `:jspecify-annotations`, but I don't think it's necessary, as we...

Done.

This is written in the docs-1.0 branch, which we'll merge into main soon.

@kevinb9n any luck finding it?

**Decision:** JSpecify requires conformant tools to recognize nullness issues even when there are also Java unchecked warnings for the same reason. Tools do not have to report the nullness issues...

That bit.ly link appears to go to a heading that no longer exists in the doc.

@dependabot rebase

Are we planning any pre-1.0 releases? If they're not necessary, I'd rather not. @kevinb9n, do you have any strong opinions here?

At this point I don't see any reason not to just jump to 1.0.