Replies: 4 comments 6 replies
-
|
I think this is a great idea, a few ideas for additional criteria for our Milestones:
We should probably add one of these:
Or:
I have seen both of these work. Having both PRs and issues is more natural and people tend to gravitate towards that, but it can be hard to refine a milestone with PRs + issues. I do think that if PRs and issues are both allowed, then we should only allow "singleton" PRs. This means that if someone opens an important PR without an issue, it can be in the milestone. However, an issue and its associated PRs should not both be in the milestone. |
Beta Was this translation helpful? Give feedback.
-
|
Should we mention something about how discussion about a release will be managed -- right now we do this ad-hoc in the Releases channel. |
Beta Was this translation helpful? Give feedback.
-
|
This looks very good @raghotham - I would maybe make one addition stating something like "this process will be displayed in |
Beta Was this translation helpful? Give feedback.
-
|
Is this a good opportunity to clarify a few more things like:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As discussed in the community office hours on 11/20, we would like to add a lightweight project planning process for llama stack so that we can provide some level of predictability to the community on what to expect by when.
As a first iteration, here's what we could have:
Schedule for releases
Milestones
Release process
Beta Was this translation helpful? Give feedback.
All reactions