Skip to content
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

[Release] Manage DataFed v2025.2.12.14.01 Release #1248

Open
AronPerez opened this issue Jan 22, 2025 · 3 comments · May be fixed by #1296
Open

[Release] Manage DataFed v2025.2.12.14.01 Release #1248

AronPerez opened this issue Jan 22, 2025 · 3 comments · May be fixed by #1296
Assignees
Labels

Comments

@AronPerez
Copy link
Collaborator

AronPerez commented Jan 22, 2025

Description

This ticket is a placeholder for managing the DataFed release. Its goal is to keep everyone on the same page about the release and clarify any concerns or questions.

Steps to Follow

  1. Following the provided documents below, we will coordinate and release a new version of DataFed.
  2. We will ensure a 2-day code freeze to QA before deploy.
  3. Code freeze on Fed 3rd on the release branch

Resources

@AronPerez AronPerez added Priority: Medium Above average priority Status: Blocked Issue is blocked by another issue or external factor labels Jan 22, 2025
@AronPerez
Copy link
Collaborator Author

Blocked by #1240

@AronPerez
Copy link
Collaborator Author

Blocked by #1252

@AronPerez
Copy link
Collaborator Author

Blocked by #1240

Merged

@AronPerez AronPerez added Priority: High Highest priority and removed Priority: Medium Above average priority Status: Blocked Issue is blocked by another issue or external factor labels Feb 10, 2025
@AronPerez AronPerez linked a pull request Feb 10, 2025 that will close this issue
@AronPerez AronPerez changed the title [Release] Manage DataFed x.x.x Release [Release] Manage DataFed v2025.2.12.14.01 Release Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants