Our group is planning to keep working on this project after the end of the semester, so we have issues and milestones open that we only plan to work on after the proper submission. (They are mostly for adding further features or refactoring existing code, not bugs we currently have.)
Will doing this complicate project grading in any way?
You are more than welcome to continue working on the project. However, take note of the following:
All issues not belonging to the product in its current form should be assigned v2.0 milestone explicitly.
You have a 14 day freeze period after submission; no changes to the code /documentation (or the repository) are allowed. You need to seek approval to make any changes within that time range (and usually that would be considered a late submission)
Our group is planning to keep working on this project after the end of the semester, so we have issues and milestones open that we only plan to work on after the proper submission. (They are mostly for adding further features or refactoring existing code, not bugs we currently have.)
Will doing this complicate project grading in any way?