-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
1.9.0-jumbo-2 #3979
Comments
We lack developers! These are tasks I can't handle:
|
Aye. The TS is good but it needs some rework (IIRC there are ideas/issues in that repo). I don't have time for that at all but if we had a dedicated volunteer I could probably spew out tens of enhancement ideas. Right now I think its For testing edge case and other stuff, the original functionality is better but needs some work for every new format. |
What hardware do we need and why?
There's no option of that name in core, but regardless what's wrong with core's self-test? |
I'm using the "coming from core" terminology seen at: #3776 (comment) Also, see #948
We have no Windows users here (GitHub) telling us how JtR is behaving. No developers using BE hardware. No more developers trying GPUs and drivers. Or, what about 32bits Windows OpenCL. |
#948 is definitely not 1.9.0-jumbo-2 material unless we happen not to make that release for a very long time, in which case it'd probably need to have a different number anyway. I've just changed the target milestone on that issue. I think the lack of testing by actual users (or developers) is very different from a lack of hardware. |
I've just moved many issues out of the 1.9.0-jumbo-2 milestone, but many of the remaining ones give me a "probably not now" feeling as well. We probably need separate milestones for "definitely 1.9.0-jumbo-2 material" vs. "potentially 1.9.0-jumbo-2 material". |
Note to self: Update |
I think I did all the above. Not sure what's on the Jumbo-2 prio but I will now re-visit #3498 just because I really really want to. It will definitely take a while before you see anything at all from me again (at least in that context) but when that happens, things might move quickly. |
Discussion restarted in new context in #4564. Closing this one. |
I just renamed the milestone "Later than jumbo-1" to "Later than jumbo-2".
Please review 1.9.0-jumbo-2 and Later than 1.9.0-jumbo-2 and move stuff between them as needed.
The text was updated successfully, but these errors were encountered: