Skip to content
This repository has been archived by the owner on Oct 15, 2024. It is now read-only.

Milestones kdb-record #4463

Closed
1 of 3 tasks
atmaxinger opened this issue Sep 12, 2022 · 5 comments
Closed
1 of 3 tasks

Milestones kdb-record #4463

atmaxinger opened this issue Sep 12, 2022 · 5 comments
Assignees
Labels

Comments

@atmaxinger
Copy link
Contributor

atmaxinger commented Sep 12, 2022

This issue is for tracking my milestones

  • M1 - 1.10.2022 - finalized use cases/begin of implementation. Global plugins should work in new-backend branch.
  • M2 - 12.12.2022 - working implementation/begin of case studies. Submitted introduction, methodology and description of case studies for review.
  • M3 - 6.2.2023 First Draft of Thesis
@atmaxinger atmaxinger self-assigned this Sep 12, 2022
@markus2330
Copy link
Contributor

Please also write for M2 which parts of the thesis you want to submit, e.g. introduction and methodology.

About Implementation: I assume everything related to new-backend is M1, everything else is M2 and M3 is for left-overs?

@atmaxinger
Copy link
Contributor Author

Hmm yes it would probably make sense to have the Methodology, Introduction and the description of the Case Studies finished by M2.

Regarding the Implementaion: originally everything including new-backend was planned for M2, but if we want to merge it by October then yes M1 would make much more sense for reparing the current global plugins.

Yes, at M3 implementation should be completely finished, including all bugs that I found during the execution of the case studies.

@markus2330
Copy link
Contributor

Sounds good to me! 🚀

@github-actions
Copy link

github-actions bot commented Oct 7, 2023

I mark this stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping by writing a message here or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

@github-actions github-actions bot added the stale label Oct 7, 2023
Copy link

I closed this now because it has been inactive for more than one year. If I closed it by mistake, please do not hesitate to reopen it or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants