release is now Monday

[findtopher]

What changes are proposed in this pull request?

bump release notes dates

How is this patch tested? If it is not, please explain why.

I read it

Release Notes

Is this a user-facing change that should be mentioned in the release notes?

• No. You can skip the rest of this section.
• Yes. Give a description of this change to be included in the release
  notes for FiftyOne users.

(Details in 1-2 sentences. You can just refer to another PR with a description
if this PR is part of a larger change.)

What areas of FiftyOne does this PR affect?

• App: FiftyOne application changes
• Build: Build and test infrastructure changes
• Core: Core fiftyone Python library changes
• Documentation: FiftyOne documentation changes
• Other

Summary by CodeRabbit

• New Features

  • Video playback now supports the timeline API.
  • Utilities added for a rerun panel.
  • Enhanced functionalities in FiftyOne Teams and Core sections.

• Bug Fixes

  • Resolved issues with Auth0 connections behind proxies.
  • Fixed rendering issues for Classifications labels.
  • Addressed launch issues with fiftyone quickstart and fiftyone app launch commands.
  • COCO exports now utilize 1-based categories.

• Release Date Updates

  • FiftyOne Teams 2.1.1 and FiftyOne 1.0.1 release dates updated to October 14, 2024.

[coderabbitai]

Walkthrough

The pull request updates the release notes for the FiftyOne platform, specifically for versions FiftyOne Teams 2.1.1 and FiftyOne 1.0.1. Key changes include a revised release date for both versions from October 11, 2024, to October 14, 2024, and updates to dependencies and bug fixes. Notable improvements include enhanced video playback, utility additions for rerun panels, and fixes for rendering issues and command launches. Additionally, the release notes for earlier versions, 2.1.0 and 1.0.0, have been included.

Changes

File	Change Summary
docs/source/release-notes.rst	Updated release dates for FiftyOne Teams 2.1.1 and FiftyOne 1.0.1; added bug fixes and new features for both versions; included details for versions 2.1.0 and 1.0.0.

Possibly related PRs

• Release notes v1.0.1 #4898: This PR updates the release notes for FiftyOne Teams 2.1.1 and FiftyOne 1.0.1, which includes the same changes regarding the Auth0 connections and the dependency requirement for voxel51-eta as noted in the main PR.
• Merge release/v1.0.1 to develop #4911: This PR also introduces updates to the release notes for versions 2.1.1 and 1.0.1, reflecting the same changes related to bug fixes and dependency updates as described in the main PR.

Suggested labels

documentation

Suggested reviewers

• benjaminpkane

🐇 In the meadow, the notes do bloom,
With fixes and features, they chase away gloom.
Teams and versions, all in a line,
A hop and a skip, the updates now shine!
From bugs to dependencies, all is set right,
Celebrate the changes, oh what a delight! 🌼

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 233689b and 4aa3ab1.

📒 Files selected for processing (1)

• docs/source/release-notes.rst (2 hunks)

🧰 Additional context used

🔇 Additional comments (6)

docs/source/release-notes.rst (6)

Line range hint 8-24: Significant updates in FiftyOne v0.23.8

This release introduces several important features and improvements:

1. A new Hugging Face Hub integration for publishing and downloading datasets.
2. Support for visualizing and interacting with GeoLocation data in a new Map panel.
3. Improved performance and user experience in various App components.
4. Several bug fixes and optimizations in the Core functionality.

These changes enhance FiftyOne's integration capabilities and improve its overall performance and usability.

---

Line range hint 26-56: Core improvements and new features in v0.23.8

1. Added support for date and datetime operations in the view expression API, enhancing data filtering and analysis capabilities.
2. Introduced new set operations for the view expression API, improving data manipulation options.
3. Improved the robustness of concurrent schema updates and other database operations.
4. Enhanced support for working with video datasets, including frame selection and matching.

These additions significantly expand FiftyOne's data handling and querying capabilities.

---

Line range hint 58-71: Zoo and plugin enhancements in v0.23.8

1. Added support for YOLOv8 and YOLOv9 segmentation models in the Model Zoo.
2. Improved plugin functionality, including better error handling and support for custom components.

These updates expand the available models and improve the extensibility of FiftyOne.

---

Line range hint 73-95: Key updates in FiftyOne v0.23.7

1. Fixed several App-related bugs, improving stability and user experience.
2. Added new integrations and datasets to the Zoo, including Places2 and YOLOv8/YOLOv9 models.
3. Improved documentation, including new tutorials and examples.

These changes address important issues and expand FiftyOne's capabilities and ease of use.

---

Line range hint 97-185: Major features and improvements in FiftyOne v0.23.6

1. Introduced Redis and MongoDB integrations for native text and image searches on FiftyOne datasets.
2. Added a new V7 integration for annotating FiftyOne datasets.
3. Significant App improvements, including a new Lightning mode for optimized filtering experience.
4. Enhanced Core functionality, including support for 3D objects and rotated bounding boxes.
5. Improved Brain methods for similarity searches and uniqueness computation.

These additions greatly enhance FiftyOne's search capabilities, annotation support, and overall performance.

---

Line range hint 187-280: Noteworthy changes in FiftyOne v0.23.5 and earlier versions

1. Added support for Segment Anything and DINOv2 models in the Model Zoo.
2. Introduced PyTorch Hub integration for loading models.
3. Improved support for keypoint skeletons and custom per-point attributes.
4. Enhanced video dataset handling and visualization.
5. Added support for grouped datasets and dynamic groups.

These updates significantly expand FiftyOne's model support, improve its handling of various data types, and enhance its visualization capabilities.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.