Skip to content

Comments

Scala Testing #1663

Open
vlakshmanan-scala wants to merge 60 commits intorelease-v4.6.0from
Scala-Test
Open

Scala Testing #1663
vlakshmanan-scala wants to merge 60 commits intorelease-v4.6.0from
Scala-Test

Conversation

@vlakshmanan-scala
Copy link

The first line should be a single-line "purpose" for this change

TYPE: choose one of [bug fix, enhancement, new feature, feature removed, no impact, text only]

KEYWORDS: 5 to 10 words related to commit, separated by commas

SOURCE: Either "developer's name (affiliation)" .XOR. "internal" for a WRF Dev committee member

DESCRIPTION OF CHANGES:
Problem:
Generally or specifically, what was wrong and needed to be addressed?

Solution:
What was down algorithmically and in the source code to address the problem?

ISSUE: For use when this PR closes an issue.
Fixes #123

LIST OF MODIFIED FILES: list of changed files (use git diff --name-status master to get formatted list)

TESTS CONDUCTED:

  1. Do mods fix problem? How can that be demonstrated, and was that test conducted?
  2. Are the Jenkins tests all passing?

RELEASE NOTE: Include a stand-alone message suitable for the inclusion in the minor and annual releases. A publication citation is appropriate.

@vlakshmanan-scala vlakshmanan-scala requested a review from a team as a code owner May 4, 2022 20:40
@vlakshmanan-scala vlakshmanan-scala changed the base branch from release-v4.4.2 to release-v4.4.3 November 9, 2023 15:26
@vlakshmanan-scala vlakshmanan-scala changed the base branch from release-v4.4.3 to release-v4.5.2 November 9, 2023 15:37
@vlakshmanan-scala vlakshmanan-scala changed the base branch from release-v4.5.2 to release-v4.6.0 April 17, 2024 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants