Skip to content
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

Schedule for next Submission #168

Open
bitfort opened this issue Jan 10, 2019 · 6 comments
Open

Schedule for next Submission #168

bitfort opened this issue Jan 10, 2019 · 6 comments
Labels
Backlog An issue to be discussed in a future Working Group, but not the immediate next one.

Comments

@bitfort
Copy link

bitfort commented Jan 10, 2019

When do benchmarks freeze?
When do you submit?
Are there other deadlines?

SWG:
Initial thoughts: At least the first half of 2019 the results are published.

Other thoughts; At least a month between benchmark freeze and submission.

@bitfort bitfort added the Next Meeting Item to be discussed in the next Working Group label Jan 10, 2019
@bitfort
Copy link
Author

bitfort commented Jan 17, 2019

SWG Notes:

Tentative proposal: Freeze in early march, submit early May. Publish end of may.
AI(all submitters): Find out for next week if you really don't like this.

@bitfort bitfort added the AI There is an action item here. label Jan 24, 2019
@bitfort
Copy link
Author

bitfort commented Jan 24, 2019

SWG Notes:

"Freeze in early march, submit early May. Publish end of may." -- This is sounding better and better.
We think Fridays are good for deadlines.

A 2 month freeze was proposed (specifically for datasets and models). More discussion needed about what freezes when.

Tentative proposal: May 10th for submission. The "freeze" would be Friday March 8th (datasets and models). May 31st for ending review.

AI(everyone) check these dates.

@bitfort
Copy link
Author

bitfort commented Jan 31, 2019

SWG Notes:
Friday March 8th Slush
Friday May 10th Submission
Friday May 31st Complete review process
Monday June 3rd publication

This is our timeline for v0.6.

@bitfort bitfort added Rec: Rules Change A recommendation has been issued by the Working Group. Next Meeting Item to be discussed in the next Working Group AI There is an action item here. and removed AI There is an action item here. Next Meeting Item to be discussed in the next Working Group Rec: Rules Change A recommendation has been issued by the Working Group. labels Jan 31, 2019
@bitfort
Copy link
Author

bitfort commented Jan 31, 2019

AI(Intel) - Confirm next week.

@bitfort
Copy link
Author

bitfort commented Feb 7, 2019

SWG Notes:

Candidate compromise option: 8/9 (Friday) for 0.7 submission, keep 0.6 at 5/10 submission. This allows submitters a finer granularity in choosing which rounds to submit.

AI(Everyone) please follow up over email with how this schedule works for you.

@petermattson petermattson added Rec: Rules Change A recommendation has been issued by the Working Group. and removed AI There is an action item here. Next Meeting Item to be discussed in the next Working Group labels Feb 21, 2019
@petermattson petermattson added Backlog An issue to be discussed in a future Working Group, but not the immediate next one. and removed Rec: Rules Change A recommendation has been issued by the Working Group. labels May 29, 2020
@petermattson
Copy link
Contributor

Moving this into backlog instead. We need a generic deadline set given a stable cadence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backlog An issue to be discussed in a future Working Group, but not the immediate next one.
Projects
None yet
Development

No branches or pull requests

2 participants