Repository navigation
Update ICDAR 2027 - #3360
Update ICDAR 2027#3360jacklightChen wants to merge 1 commit into
Conversation
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Welcome to ccf-deadlines! |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6eb497c9e0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
ViGeng
left a comment
ViGeng
left a comment
There was a problem hiding this comment.
Hi @jacklightChen, Im just catching up the context. why would we change from 59:59 to 59:00?
Changes
Preserve the officially stated 23:59 AoE cutoff for the regular conference-paper track instead of applying the date-only 23:59:59 default:
Official evidence
https://icdar2027.org/call-for-papers explicitly states that all listed deadlines are strict at 23:59 AOE, and lists these dates together. This is the full-length original-research conference track. https://icdar2027.org/important-dates agrees on the dates. Edition, Kuala Lumpur location, August 18–22 meeting dates and AoE timezone remain unchanged. Existing journal-track data is untouched.
Validation
YAML/schema validation, scripts/validate.py and git diff --check passed. Remote CI has not yet been verified.