Document PyMC 4.0 release and key innovations#118
Open
vishalmore90 wants to merge 1 commit intopymc-devs:mainfrom
Open
Document PyMC 4.0 release and key innovations#118vishalmore90 wants to merge 1 commit intopymc-devs:mainfrom
vishalmore90 wants to merge 1 commit intopymc-devs:mainfrom
Conversation
Added detailed explanation of PyMC 4.0 release and its features.
{ref}v4_announcement cross‑reference that the TODO mentioned.---### Step 4: Add a new “Version 5” section Using the v5.0.0 release notes and PyTensor announcement as references ([v5.0.0 release](https://github.com/pymc-devs/pymc/releases/tag/v5.0.0)[^v5], [PyTensor announcement](https://www.pymc.io/blog/pytensor_announcement.html)[^pytensor]), append a new section directly after Version 4:``markdown
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added detailed explanation of PyMC 4.0 release and its features. {ref}v4_announcement cross‑reference that the TODO mentioned.---### Step 4: Add a new “Version 5” section Using the v5.0.0 release notes and PyTensor announcement as references (v5.0.0 release[^v5], PyTensor announcement[^pytensor]), append a new section directly after Version 4:``markdown