Esri / Esri/ops-server-config

What is the Ops Server Fall Release Schedule? + Repo Release Admin Tasks Reminders

Open
#1,012 0 comments 0 reactions 0 assignees View on GitHub
0 - Backlog B - Question G - Release Team
Dominant language
Python
Stars
33
Forks
12
PR merge metrics
No merged PRs in 30d

Description

@csmoore Removed screen because it had internal server name.

(@dfoll wanted to share this)

As part of this release, just a few reminders (in case not already captured elsewhere):
- [ ] Scrub all the issues (ex. put closed issues into the v.next milestone since they are already done, move open ones you aren't doing to "version after next")
- [ ] Once done testing, merge v.next into master
- [ ] Actually create a Github release for this repo

---

In case needed, here are the detailed steps from OneNote (but just ping me when ready to do and I will step you through this the first time so it is clearer/easier to understand)
- [ ] Review the Open Issue List as a group/team
1. Determine if there are any showstoppers
2. Move any incomplete+optional items into the next release milestone ("Version - After Next")
3. Move any closed issues into Version - Next
- [ ] Sanity Check/Test the release
- [ ] Create Pull Request (within Esri repo) to Merge Branch "v.next" into -> Branch Master
- [ ] In Issues | Milestones, rename Milestone "Version – Next" to "Release X.X.X" (X.X.X = whatever the version is) and close the milestone (recheck that there are no open issues)
- [ ] In Issues | Milestones, rename Milestone "Version After Next" to "Version Next"
- [ ] In Issues | Milestones, create a new "Version After Next" milestone
- [ ] Create Github Release (using the same "Release X.X.X" name used above) against the Master branch
1. In your release description, provide a link to the Milestone, so the issues fixed get included there: ex: `https://github.com/Esri/ops-server-config/milestones/ReleaseX.X.X`

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the repository's open issue list and the Version - Next and Version After Next milestones. Follow the listed release checklist: sanity-check the release, merge v.next into master, update the milestones, and create the matching GitHub release. The issue provides process reminders but no code files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
release
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.