https://pinot.apache.org/ logo
Join Slack
Powered by
# release-1-dot-3
  • x
    Sounds good! As always, the wiki is always out-dated, feel free to update it and optimize/simplify it whatever
  • a
    Hi Everyone, I am planning to cut the Pinot 1.3 Release from HEAD on Jan 11. All the commits merged into master branch before EOD on Jan 10 will be part of the release. Thanks
    x
    • 2
    • 2
  • a
    @Jackie FYI.
  • p
    Do we know what major/minor features are already going to be part of this release?
    a
    • 2
    • 9
  • s
    Hi Folks - Who is driving the release ?
    p
    • 2
    • 1
  • s
    I ask because we had fixed a security vulnerability (externally reported) to which we have responded stating that the fix will be available as part of a release in Jan and they should not disclose this as a 0-day vulnerability
    a
    x
    • 3
    • 6
  • a
    Reminder, tomorrow EOD, I will cut the 1.3.0 version release candidate.
  • r
    @Abhishek Sharma Could this PR be merged if possible before release cut? https://github.com/apache/pinot/pull/14755
    a
    • 2
    • 3
  • a
    Hi Folks, I have a question around release-notes, do we review them before posting?
    x
    g
    • 3
    • 10
  • a
    Hey Everyone, here is the draft version of the release candidate 1.3.0. Please have a look and let me know if anything needs a change or update. I will publish it based on the feedback. Thanks
    m
    • 2
    • 2
  • a
    Hi Everyone 👋, Apache Pinot 1.3.0 RC0 is out for voting, please give it a try and share the feedback. Thanks
  • a
    Hi, Please guide here .. What should be the next step with the release since candidate is out for almost six days or so?
  • x
    Let me ping people around for the validation. We need to get at least 3 +1s
  • g
    Any chance we can include this in 1.3 or maybe a 1.3.1?
    a
    • 2
    • 1
  • p
    @Abhishek Sharma Head's up! Just had a chat with @Ankit Sultana. Important to revise the release notes to state that the time series engine is currently a beta release. Ankit is looking to have another release in 1H of 2025 for GA of this feature. I'll let the two of you work out specifically how this should be worded.
  • p
    @Abhishek Sharma: If you haven't already, you might want to check with other feature committers to review the sections of the release notes specific to their contributions to catch if there are any other caveats that should be noted.
    a
    • 2
    • 1
  • a
    ^ I was even saying that we should call it "Experimental" for now. I'll change some SPI contracts over the next month or so for the time series engine, and if anyone starts using it then they might not be happy if we do that 😅
  • a
    @Peter Corless: I think you'd know which one is more apt: I think Beta covers all grounds, but if it doesn't then we can go with Experimental
  • p
    I think "Experimental" sounds better for a specific feature. "Beta" usually applies to a whole release.
  • p
    Let me check with some other folks that have opinions and see how they weigh in.
  • p
    @Ankit Sultana Any progress on updating the release notes? How's the vote going?
    a
    s
    • 3
    • 10
  • a
    It seems that we have to release next version of RC as we found some issues with RC0. Apart of PR-14848 and PR-14842, any other changes we want to merge?
    s
    g
    c
    • 4
    • 7
  • a
    Hi Everyone, New release candidate RC1 for 1.3.0 release is out. Here is the pre-release link. Also, the voting email is out with details. Please have a look. Thanks
    s
    • 2
    • 4
  • p
    @Abhishek Sharma Two issues that seem to have gotten merged, but aren't mentioned in the 1.3.0 release notes: • https://github.com/apache/pinot/pull/14858 • https://github.com/apache/pinot/issues/14305 Can you clarify?
    a
    • 2
    • 2
  • m
    @Abhishek Sharma any ETA on the release?
    a
    y
    s
    • 4
    • 12
  • a
    Yesterday, we completed the voting phase for the release. There wasn't any negative vote, and we Passed the voting. We are now executing the next phase of the release as per the doc . Thanks
    m
    • 2
    • 4
  • p
    Congrats @Abhishek Sharma! And thank you to all the contributors to the release!
    a
    • 2
    • 1
  • a
    FYI
  • s
  • p
    @Abhishek Sharma ☝️