-
Notifications
You must be signed in to change notification settings - Fork 26
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
Take the Javadoc warning down a notch #491
Comments
I was just about to ask about this. On the repo home page / README you have:
But then I read the Javadoc and started to question whether it's time yet. Is there somewhere I can read about the remaining obstacles to a 1.0 version? |
Glad you're interested! You can filter issues by the 1.0 milestone. That should at least trend toward accurate. However, there is an ambiguity between the jar going 1.0 and the spec going 1.0; there are several minor changes that can happen to the latter without any effect on the former. I'm not sure if we accounted for that in how we apply the milestone to issues. |
For this issue I set the milestone to 1.0 but it's actually "the sooner the better", doesn't need to wait. |
Honestly, what happens if we just remove this warning completely? |
More users? 🙃 |
Oh, never mind then. 🤣 |
That warning btw I have seen cited on reddit and various places and the general outcome seems to be unfavorable inhibition even for library authors like myself. Anyway I'm for more users 😄 |
So my 3¢: I was just thinking about using nullness annotations and wanting to go with something standard but after reading both readme and wiki I wasn't so sure. Then I looked at milestone for 1.0 which sits at ~50% so from the cursory look it's really hard to figure out if one should adopt it or not. Alas, it seems that 1.0 is closer than further so it should be OK to adopt it :-) |
Currently we have
This seems overstated at this point, yes?
The text was updated successfully, but these errors were encountered: