Skip to content

Release notes to sprint 60 #483

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

Merged
merged 31 commits into from
Oct 22, 2024
Merged

Conversation

nrichers
Copy link
Collaborator

@nrichers nrichers commented Oct 18, 2024

Internal Notes for Reviewers

This PR includes release notes up to Sprint 60: LIVE PREVIEW — October 22, 2024

Frontend

Developer framework

Documentation

Other improvements

New button class for Markdown links

I got tired of our hard-coded HTML buttons and added a new class for buttons to simplify the process. You can now add {.button} to any Markdown link to turn it into a button:

image
Before After
<form method="get" action="../../guide/monitoring/ongoing-monitoring.html"><button type="submit" style="color: white; background-color: #de257e; border-radius: 8px; border: none; font-size: 16px; padding: 6.25px 12.5px; margin-left: 16px; margin-bottom: 20px;">Learn about monitoring</button></form> [Learn about monitoring](../../guide/monitoring/ongoing-monitoring.qmd){.button}

Rounded edges for screenshots

Quite subtle, but our class="screenshot" was very rectilinear. I added the same rounding for corners as for the button:

Before After
image image

External Release Notes

@nrichers nrichers added the internal Not to be externalized in the release notes label Oct 18, 2024
Copy link
Contributor

A PR preview is available: Preview URL

Copy link
Contributor

PR Summary

This pull request introduces several enhancements and bug fixes to the ValidMind platform, focusing on improving user experience, functionality, and documentation.

Key Enhancements

  1. Support for Ongoing Monitoring: Introduces ongoing monitoring for model risk management, allowing users to enable monitoring for both existing and new models. This feature includes a new notebook for logging monitoring results.

  2. Archive and Delete Models: Adds functionality to archive and delete models, helping maintain an accurate model inventory. Archived models are read-only and can be restored by an administrator.

  3. Bias and Fairness Tests: Introduces new metrics for evaluating model bias and fairness, along with a new Jupyter Notebook for hands-on analysis.

  4. Metric Over Time Content Block: Adds a new content block type for displaying metrics over time, enhancing model documentation and monitoring.

  5. Column Filtering in Tests: Allows filtering of specific columns when running tests, simplifying data analysis.

  6. Email Verification Improvements: Enhances the email verification process with a new error page and resend functionality.

  7. Custom Field Management: Enhances custom field functionality with Python support, a new code editor, and testing features.

  8. Attachment Management: Introduces attachment fields for model inventory and findings, with enhanced permissions for managing attachments.

  9. New Currency Field Type: Adds a currency type for number fields, allowing for formatted currency data.

  10. Delete Finding Button: Allows validators to delete findings with confirmation dialogs and error handling.

  11. Role Management Enhancements: Enables renaming and editing of organization roles, except for the Customer Admin role.

  12. Model Activity Filtering: Improves filtering options for model activity logs, making it easier to find relevant information.

  13. Rich Text Editor for Validation Guidelines: Introduces rich text editing for validation guideline descriptions, improving content management.

Bug Fixes

  • Scrollbar Display on Windows: Fixes an issue with unnecessary scrollbars in the layout sidebar on Windows, improving the user interface.

Documentation Updates

  • Training Content: Updates training modules with a new color scheme and improved navigation.
  • Model Validation Videos: Adds a series of videos to guide users through the model validation process.
  • Deployment Options Overview: Expands documentation on deployment options for ValidMind.
  • GitHub Link for Code Samples: Adds a link to the code samples page for easier access to open-source software.

Test Suggestions

  • Test the ongoing monitoring feature by enabling it for a model and verifying data population in the monitoring template.
  • Verify the archive and delete functionality by archiving a model and attempting to delete it.
  • Run bias and fairness tests using the new metrics and confirm the results are as expected.
  • Add a 'Metric Over Time' block to model documentation and check the display of metrics over a specified time range.
  • Test column filtering in dataset tests to ensure only selected columns are analyzed.
  • Simulate an email verification error and verify the new error page and resend functionality.
  • Create and test a custom field with Python code to ensure correct execution and output.
  • Add and manage attachments in model inventory and findings, checking for correct permissions.
  • Create a currency field and verify the formatting and precision settings.
  • Delete a finding and confirm the confirmation dialog and error handling work correctly.
  • Rename an organization role and verify the changes are reflected in the settings.
  • Filter model activity logs and ensure the filters work as intended.
  • Use the rich text editor for validation guidelines and check the formatting capabilities.

Copy link
Contributor

PR Summary

This pull request introduces several enhancements and bug fixes to the ValidMind platform, focusing on improving user experience, functionality, and documentation.

Key Enhancements

  1. Support for Ongoing Monitoring: Introduces ongoing monitoring for model risk management, allowing users to enable monitoring for both existing and new models. This feature includes a new notebook for logging monitoring results.

  2. Archive and Delete Models: Adds functionality to archive and delete models, helping maintain an accurate model inventory. Archived models are read-only and can be restored by an administrator.

  3. Bias and Fairness Tests: Introduces new metrics for evaluating model bias and fairness, along with a new Jupyter Notebook for hands-on analysis.

  4. Metric Over Time Content Block: Adds a new content block type for displaying metrics over time, enhancing model documentation and monitoring.

  5. Column Filtering in Tests: Allows filtering of specific columns when running tests, simplifying data analysis.

  6. Email Verification Improvements: Enhances the email verification process with a new error page and resend functionality.

  7. Custom Field Management: Enhances custom field functionality with Python support, a new code editor, and testing features.

  8. Attachment Management: Introduces attachment fields for model inventory and findings, with enhanced permissions for managing attachments.

  9. New Currency Field Type: Adds a currency type for number fields, allowing for formatted currency data.

  10. Delete Finding Button: Allows validators to delete findings with confirmation dialogs and error handling.

  11. Role Management Enhancements: Enables renaming and editing of organization roles, except for the Customer Admin role.

  12. Model Activity Filtering: Improves filtering options for model activity logs, making it easier to find relevant information.

  13. Rich Text Editor for Validation Guidelines: Introduces rich text editing for validation guideline descriptions, enhancing content management.

Bug Fixes

  • Scrollbar Display on Windows: Fixes an issue with unnecessary scrollbars in the layout sidebar on Windows, improving the user interface.

Documentation Updates

  • Training Content: Updates training modules with a new color scheme and improved navigation.
  • Model Validation Videos: Adds a series of videos to guide users through the model validation process.
  • Deployment Options Overview: Expands documentation on deployment options for ValidMind.
  • GitHub Link for Code Samples: Adds a link to the code samples page for easier access to open-source software.

Test Suggestions

  • Test the ongoing monitoring feature by enabling it for both new and existing models.
  • Verify the archive and delete functionality for models, ensuring models can be archived, deleted, and restored.
  • Evaluate the bias and fairness tests using the new metrics and Jupyter Notebook.
  • Test the 'Metric Over Time' content block by adding it to model documentation and monitoring.
  • Run tests with column filtering to ensure only specified columns are analyzed.
  • Check the email verification process, including the new error page and resend functionality.
  • Test the custom field management with Python support, including the code editor and testing features.
  • Verify attachment management in model inventory and findings, ensuring permissions are respected.
  • Test the new currency field type for number fields, checking formatting and precision options.
  • Ensure the delete finding button works as expected, with proper confirmation and error handling.
  • Test role management enhancements by renaming and editing roles, except for the 'Customer Admin' role.
  • Verify model activity filtering options for accuracy and ease of use.
  • Test the rich text editor for validation guidelines, ensuring content is displayed and managed correctly.

Copy link
Contributor

A PR preview is available: Preview URL

Copy link
Contributor

A PR preview is available: Preview URL

Copy link
Contributor

A PR preview is available: Preview URL

Copy link
Contributor

A PR preview is available: Preview URL

@nrichers
Copy link
Collaborator Author

nrichers commented Oct 21, 2024

@validbeck, great feedback, thank you. Will address where you haven't already. Some comments:

We've being using target="_blank for CTA links out of release notes, FYI. Can you please add these?

I don't think this should be true globally. We should open links in new tabs ONLY if the links are external and this is already configured in _quarto.yml via link-external-newwindow: true. Links to other pages in the docs should not be spawning tabs for the docs site all over the place, especially given how many links we now have. Less is more.

(For reference, at my previous gig we had a rule that internal docs links could never spawn another tab, as we had >300k pages and it was just messy otherwise. You can always open links in a new tab if this is your preference.)

We need some links to the metric test reference pages!
Needs a link to the DatasetDescription reference.

I'm on the fence about these but with a preference not to add too many links — release notes should tell you how to get started with something after you read them and that should be the notebooks, not some reference page. Again, less is more.

@validbeck
Copy link
Collaborator

Forgot to mention, I like the new rounded corners!

I don't think this should be true globally. We should open links in new tabs ONLY if the links are external and this is already configured in _quarto.yml via link-external-newwindow: true. Links to other pages in the docs should not be spawning tabs for the docs site all over the place, especially given how many links we now have. Less is more.

This is how the buttons were when I grabbed them to do the first round of links — I will adjust in my PR now that I know this wasn't intentional.

I'm on the fence about these but with a preference not to add too many links — release notes should tell you how to get started with something after you read them and that should be the notebooks, not some reference page. Again, less is more.

I understand what you're arguing, but in this case I vote for them. As a developer, I would expect to see the reference for the function or test you're talking about.

@nrichers
Copy link
Collaborator Author

This is how the buttons were when I grabbed them to do the first round of links — I will adjust in my PR now that I know this wasn't intentional.

I think that was likely a side effect of which button you grabbed to create others which just goes to show that there is an issue with the old HTML button approach. Thank you for fixing!

I understand what you're arguing, but in this case I vote for them. As a developer, I would expect to see the reference for the function or test you're talking about.

Will add for now but we should discuss the meaning of the tip of the iceberg that is release notes ... Reference content on its own likely is not enough to do something, so why not just link to something you can actually use out of the box?

General thoughts on links in release notes, for further discussion:

  • The user journey into a feature should guide you clearly — It shouldn't start with a bunch of doors you have to choose from at the beginning. That means fewer links with a clear path, not more options.
  • Progressive disclosure tells us to provide reference links in the context where they matter — i.e., in the notebook itself, where we show you how to use a function or metric.
  • Release notes should feel clean and simple — Linking maximalism is the antithesis of that. (This might partly be a repeat comment on a recent PR where we added scores of new buttons. I think they add clutter, increase authoring cost, and most will likely never be clicked.)
  • Treat release notes as if they had an expiration date — Related to the previous point, release notes are like water under the bridge: once something has been published, it receives fewer and fewer eyeballs over time. The real value lies in the core documentation for a feature that sticks around and where people will look for information.
  • Don't forget the authoring cost — Release notes are expensive to author to begin with, and we should limit how much time we spend on them. Looking up reference content links is fairly low on the bang-for-the-buck scale (and if the release notes are the only place where they can find a link, that's a bug and not a feature).

All of which goes to say: use links sparingly, including in release notes.

Copy link
Contributor

A PR preview is available: Preview URL

@nrichers
Copy link
Collaborator Author

Forgot to mention, I like the new rounded corners!

@validbeck I rounded the corners a bit more via df602de which also happens to solve the issue we've been having with corner artefacts from screenshots on macOS.

Before After
image image

Copy link
Contributor

A PR preview is available: Preview URL

Copy link
Contributor

A PR preview is available: Preview URL

@nrichers
Copy link
Collaborator Author

nrichers commented Oct 21, 2024

GLOBAL COMMENTS

  • We've being using target="_blank for CTA links out of release notes, FYI. Can you please add these?

Removed from the style guide, where you had added target="_blank as guidance.

  • I don't like the "Try it..." or "Learn about..." especially without the name of the link, and as we indicate in our style guide, nebulous/clumsy links should be avoided. For example, this is what I ended up doing in the clean-up:
    Screenshot 2024-10-21 at 8 59 19 AM (If there is a user guide, just use the name of the guide! No need for a lead-in.)

I replaced all the docs links with the actual topic title and I think that is a generally good rule to follow, thank you.

I do NOT agree with adding lead-in text for a button that describes what the button does ... That's just a simpler button replaced with text + button. As a general rule, we should be mindful about avoiding unnecessary verbiage — less is more!

Also, we have some notebooks that have very long titles that themselves need to be edited and that would make for some pretty painful buttons:

image

Here's how the buttons now look — doc links use the exact title and notebook links remain as before:

image
  • I also don't like the FA icons, too busy. Please remove them.

Agreed, removed.

They're the exact same size as in the docs ... If people want a bigger view, they can just watch the videos on YouTube.

  • I would break up some of the more chunkier paragraphs into some bullet points.

I scanned the text and searched for paragraphs of >200 words. I find release notes often look fragmented anyway, so I made no changes here but if there are specific sections where you think this would help, go ahead.

  • The _how-to-upgrade.qmd includes is in main, so you might need to pull in to retrieve it so you can append it at the end.

Yup, that fixed it! Not sure why it was missing when I created the release notes initially but the file is there now.

Section comments

Support for ongoing monitoring

  • The screenshot here needs to be cropped ;)

I would normally agree but in this case there is a new "Ongoing Monitoring" option in the navigation on the left that you would not see if you cropped the screenshot. (FWIW, the docs for ongoing monitoring use only a very cropped version that has been reduced to the graph.)

  • I'd also do a two column for the image with all the text up to "The monitoring template for your model automatically populates with data as your code runs..." and see what that looks like.

Since the screenshot is not being cropped, I'm going to leave this as is. I think it's fine to have a full-width screenshot here as ongoing monitoring is basically our halo feature in these release notes.

Support for bias and fairness tests

We need some links to the metric test reference pages!

Links added.

New Metric Over Time content block

The three screenshots are two cramped. I'd try two rows:

  1. Text | Adding a new block & CTA link (button should be centered)
  2. Selecting the block | Metric over time graph

Agreed, looks better in two columns, with a bit of padding between them.

Coincidentally, I noticed that you've been adding this in some places:

::: {.w-10-ns}
<!-- FILLER COLUMN DO NOT REMOVE -->
:::

These spacer columns should not be necessary with Tachyons CSS, you can use .pr1 or .pl1 to pad columns as needed, see https://tachyons.io/docs/layout/spacing/.

Filtering columns when running tests

Needs a link to the DatasetDescription reference.

Link added.

Enhanced custom field management with Python support

This video needs the styling we apply to all videos.

Ugh, done. I sense another CSS class ... manually adding video styling is getting old fast!

Rich text editor for validation guidelines

The columns here are squished.

As in there's not enough margin? I did add .pr4 to the left column but if there's something else you meant, let me know.

Updated training content

I don't know what this comment means? It's not a screenshot, it's the live training page embedded in the release notes. I did look at the example, but it's just a small callout. I'd prefer to give more emphasis to our training page here.

  • The column widths could also be adjusted to be a bit neater.

Fixed.

Copy link
Contributor

A PR preview is available: Preview URL

Copy link
Contributor

A PR preview is available: Preview URL

1 similar comment
Copy link
Contributor

A PR preview is available: Preview URL

Copy link
Contributor

A PR preview is available: Preview URL

Copy link
Contributor

A PR preview is available: Preview URL

@nrichers nrichers merged commit 3798d37 into main Oct 22, 2024
5 checks passed
@nrichers nrichers deleted the nrichers/sc-6860/release-notes-to-sprint-60 branch October 22, 2024 23:07
nrichers added a commit that referenced this pull request Oct 23, 2024
* Edits up until Releases

* Edits for 2024-aug-13 releases

* Adjusted figcaption to center text

* Edits for 2024-jul-22 releases

* Edits for 2024-jun-10 releases

* Edits to overview guides

* Releases tweaks up to June 10 2024

* Edits to march 27 2024 wip

* Final tweaks to march 27 2024

* Edited feb 14 2024

* Edited jan 26 2024

* Edited jan 18 2024

* May 22 2024 releases WIP

* Edited may 22 2024

* Added _how-to-upgrade.qmd single-source

* Added _how-to-upgrade.qmd to newer releases missing it

* Edited nov 09 2023

* Edited oct 25 2023

* WIP Sep 27 2023

* Edited Sep 27 2023

* Tweaks to variable in buttons & links

* Edited aug 15 2023

* Edited jul 24 2023

* Edited jun 22 2023

* Edited may 30 2023

* Visual tweaks

* More cleanup

* Some more tweaks

* Final? edits

* Feedback from Nik

* Maybe the python docs need to be updated on remote?

* Nope, just a docs-demo preview issue

* Release notes to sprint 60 (#483)

* Generate initial release notes

* Fix LUA error

* WIP edits

* Initial edit pass & add images

* Add new button to styles.css

* Clean up styles.css

* WIP more edits

* WIP more edits

* WIP more edits

* Update button style

* WIP edits

* Second edit pass complete

* Add button info to style guide

* Minor edits

* Fix broken link

* Run make get-source

* Final tweaks

* Remove release notes notebook

* Improved hover state for buttons

* Adjusted style guide & README

* Tweak to the convention example

* Oops, I can't spell

* Remove _blank guidance

* Round screenshot corners more

* Add fig-alt text

* Address review comments from Beck

* Add upgrade info and crop screencap

* Ambiguous antecedents are a bad habit

* Visual tweaks

* Summary & final touches

---------

Co-authored-by: Beck <164545837+validbeck@users.noreply.github.com>

---------

Co-authored-by: Beck <164545837+validbeck@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal Not to be externalized in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants