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

Roadmap for v1.0.0 #301

Open
55 of 88 tasks
bauersimon opened this issue Jul 31, 2024 · 0 comments
Open
55 of 88 tasks

Roadmap for v1.0.0 #301

bauersimon opened this issue Jul 31, 2024 · 0 comments
Assignees
Labels
roadmap Collection of issues for a release
Milestone

Comments

@bauersimon
Copy link
Member

bauersimon commented Jul 31, 2024

Highlights 🌟

  • Spring Boot πŸ₯¬ unit test support: evaluating how models generate tests for Spring
  • Code Migration πŸ” task: asking models to migrate i.e. tests from JUnit 4 to JUnit 5

Changes πŸ’‘

Details πŸ”

  • Take details from automatic release description of GitHub.

Tasks of this

❓ When should a release happen? Check the README!

  • Do a full evaluation with the version
    • Exclude certain Openrouter models by default
      • nitro cause they are just faster
      • extended cause longer context windows don't matter for our tasks
      • free and auto cause these are just "aliases" for existing models
    • Exclude special-purpose models
      • Vision models
      • Roleplay and creative writing models
      • Classification models
      • Models with internet access (usually denoted by -online suffix)
      • Models with extended context windows (usually denoted by -1234K suffix)
    • Always prefer fine tuned (-instruct, -chat) models over a plain base model
  • Tag version (tag can be moved in case important merges happen afterwards)
  • For all issues of the current milestone, one by one, add them to the roadmap tasks (it is ok if a task has multiple issues) with the users that worked on it
    • Fixed bugs should always be sorted into respective relevant categories and not in a generic "Bugs" category!
  • For all PRs of the current milestone, one by one, add them to the roadmap tasks (it is ok if a task has multiple issues) with the users that worked on it
    • Fixed bugs should always be sorted into respective relevant categories and not in a generic "Bugs" category!
  • Search all issues for ...
    • Unassigned issues that are closed, and assign them someone
    • Issues without a milestone, and assign them a milestone
    • Issues without a label, and assign them at least one label
  • Write the release notes @ https://github.com/symflower/eval-dev-quality/releases
    • Use the tasks that are already there for the release note outline
    • Add highlighted features based on the done tasks, sort by how many users would use the feature
  • Do the release
    • With release notes
    • Set as latest release
  • Prepare the next roadmap
    • Create a milestone for the next release
    • Create a new roadmap issue for the next release
      • Move all open tasks/TODOs from this roadmap issue to the next roadmap issue.
      • Move every comment of this roadmap issue as a TODO to the next roadmap issue. Mark when done with a πŸš€ emoji.
  • Blog post containing evaluation results, new features and learnings
    • Update README with blog post link and new header image
    • Update repository link with blog post link
    • https://github.com/symflower/eval-dev-quality/discussions
      • Remove the previous announcements
      • Add a "Deep dive: $blog-post-title" announcement for the blog post, unpin all others and pin this one
      • Add a "v$version: $summary-of-highlights" announcement for the release, unpin all others and pin this one
    • symflower.com
      • Update "latest DevQualityEval deep dive" mentions
      • Update DevQualityEval blog series lists with new entries
      • Update LLM blog series lists with new entries
    • Update payment process for supporting DevQualityEval
      • New Stripe payment link for this version
      • Update payment logic with new Google Drive folder of the evaluation
      • Update Payment link in this README
      • Update Payment link on symflower.com (except for the one deep dive that mentions exactly these results)
    • Create an issue in the company tracker for Markus to announce the new deep dive on Twitter and LinkedIn
  • Close this issue
  • Close the current milestone
  • Announce release
  • Eat cake πŸŽ‚
@bauersimon bauersimon added the roadmap Collection of issues for a release label Jul 31, 2024
@bauersimon bauersimon added this to the v0.7.0 milestone Jul 31, 2024
@bauersimon bauersimon mentioned this issue Sep 9, 2024
@bauersimon bauersimon changed the title Roadmap for v0.7.0 Roadmap for v1.0.0 Jan 13, 2025
@bauersimon bauersimon modified the milestones: v1.0.0, v1.1.0 Jan 15, 2025
@zimmski zimmski assigned bauersimon and unassigned zimmski Jan 15, 2025
@zimmski zimmski modified the milestones: v1.1.0, v1.0.0 Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
roadmap Collection of issues for a release
Projects
None yet
Development

No branches or pull requests

2 participants