Comments (6)
Some options:
- Detect the draft in CHANGELOG.md and update it
- I earlier suggested building up the draft release notes in the wiki and then publishing (at release time) directly from there (scripted).
- This provides the additional benefit of ease of editing and submitting and visibility on the lead up to the release
- Easy to automate API to extract formatted text from wiki
from release.
Czars and release notes maintainers past and present, please make your preference heard or make alternate suggestions.
from release.
Using a gist or wiki page and requiring an argument which is the link to the release notes SGTM
from release.
Wiki would be fine.
Need to clarify in what the exact logic would be.
- Does wiki contents get injected in between the "Downloads" and "Previous Relases included In" sections?
- Why is there no "Changelog since" section in the minor releases, and is one needed and if so how does it work.
- Should "Features" section be generated (@spiffxp what do you do?)
from release.
I used a pre-release version of https://github.com/github/hub and used the hub issues
command with a pile of bash to generate a starter list. Updates were made manually since then.
for phase in alpha beta stable; do
echo "## $phase"
echo
hub issue -l $phase-in-1.4 -f \
"- [%t](%U) (kubernetes/features%i, @%au, %as)%n";
echo
done
One of the confusing things was that I couldn't just look at the v1.4 milestones, since some feature owners had bumped them up to v1.5 to track the next iteration, eg: planning to have an alpha-in-1.4 feature turn into a beta-in-1.5 feature. Instead, I had to look at the alpha-in-1.4, beta-in-1.4 and stable-in-1.4 labels. IMO this would be way less confusing if there was one-issue-per-discrete release... eg: rather than seeing the same issue get bumped across 3 milestones as it evolves from alpha to beta to stable, have one issue for alpha, one for beta, one for stable.
agree with @david-mcmahon wiki would be a good idea, use the features repo for this, to get a PM perspective up front. I should have been able to get my one line summaries from some part of that repo instead of a spreadsheet, as much as I really appreciated the cat-herding that took.
Then, use the existing automation and labels to get more detailed technical cluster-ops-facing info.
I liked that we started this process a full week before the final bits got cut. I would encourage us to aim to have a draft of the high-level features prior to the next branch being cut.
from release.
Many of the features repo issues were less than helpful for determining what the feature actually was, and what had actually been done. if we're going to put in these massive checklists, we need to actually use them, or make them small enough that they don't scare people away
Some people linked to kubernetes.github.io PR's, others linked to the final (but not actually deplpoyed) site; this generated a lot of manual legwork for me. I ultimately manually converted everything to point to the docs staging site @devin-donnelly kindly setup. It inspired confidence that yes all the docs had actually landed, and it made it easier to regex/replace to the real site.
from release.
Related Issues (20)
- krel release-notes sometimes errors when the user exits their editor HOT 4
- Dependency update - Golang 1.21.5/1.20.12 HOT 5
- Publish kubernetes-cni v1.4.0
- kubeadm configuration file in wrong place HOT 9
- Inconsistent CI markers HOT 1
- Dependency update - Golang 1.21.6 and Go 1.20.13 HOT 3
- release-notes tool creates invalid links for some dependency entries HOT 10
- Migrate away from Google project kubernetes-release-test HOT 5
- Adopt new release of debian-base image HOT 4
- [question] about how to build images locally HOT 2
- release-notes (and release-sdk) don't check the remotes when reusing an existing temp dir for repos HOT 8
- CVE reported with distroless-iptables images HOT 9
- Dependency update - Golang 1.21.7/1.20.14 HOT 4
- Automating `krel` binary releases HOT 4
- Dependency update - Golang 1.22.1/1.21.8 HOT 8
- krel/templates: remove kubeadm's dependencies on kubelet and kubectl HOT 7
- E: The repository 'https://apt.kubernetes.io kubernetes-xenial Release' does not have a Release file. HOT 3
- The legacy Kubernetes package repositories are removed as of 2024-03-04
- few days ago the old repo has been turned off and now trying to use the new repo https://pkgs.k8s.io/core:/stable:/ fails for specific version HOT 4
- Instructions to Migrate to the Kubernetes Community-Owned Repositories Not Working HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from release.