-
Notifications
You must be signed in to change notification settings - Fork 594
Add FPT 2026 #1499
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
Add FPT 2026 #1499
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -29,3 +29,22 @@ | |||||
| timezone: AoE | ||||||
| date: December 02 - December 05, 2025 | ||||||
| place: Shanghai, China | ||||||
| - year: 2026 | ||||||
| id: fpt2026 | ||||||
| link: https://fpt2026.uark.edu/ | ||||||
| timeline: | ||||||
| - deadline: '2026-06-05 23:59:59' | ||||||
| comment: Title and Abstract Due (Conference Track) | ||||||
| - deadline: '2026-06-12 23:59:59' | ||||||
| comment: Full Paper Submission Due (Conference Track) | ||||||
| - deadline: '2026-07-17 23:59:59' | ||||||
| comment: Rebuttal Period Start (Conference Track) | ||||||
| - deadline: '2026-07-24 23:59:59' | ||||||
| comment: Rebuttal Period End / Artifact Form Due (Conference Track) | ||||||
| - deadline: '2026-05-01 23:59:59' | ||||||
| comment: Submission to ACM TRETS FPT 2026 Journal Track | ||||||
| - deadline: '2026-08-14 23:59:59' | ||||||
| comment: Notification of Acceptance | ||||||
|
||||||
| comment: Notification of Acceptance | |
| comment: Notification of Acceptance (Conference Track) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Notification of acceptance is for BOTH tracks on the same date
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The 2026 timeline is not in chronological order: the journal-track deadline (2026-05-01) appears after later June/July entries. Ordering matters in the app (e.g.,
src/components/showtable.rspicks the first upcoming deadline while iterating the YAML order, and the timeline widget assumes the first/last points are earliest/latest), so this can cause the wrong “current deadline” and a mis-rendered timeline. Reorder thetimelineentries by increasing date/time (or otherwise ensure the list is sorted chronologically).