-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
v3.2.4 cherry-pick #7171
Comments
Could you, please include in 3.2.4 #7084 ? |
Please, if you can include #7084 it would be very nice. Thanks |
Sure
…Sent from my iPhone
On Nov 4, 2021, at 8:14 PM, Yassel Avila ***@***.***> wrote:
Please, if you can include #7084 it would be very nice. Thanks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
Hi, Could you please include #6912 ? Thanks |
@sarabala1979 I think we should make, for patch release, all fixes are always added. |
@sarabala1979 Any reason why only commits made before Oct 27 are included in this? |
@sarabala1979 I think we might want an updated list? I get a different list of fixes:
f347154 (HEAD -> master, origin/master) fix: add gh ecdsa and ed25519 to known hosts (#7226) |
Agreed as long as fix doesn't have new upcoming feature changes/dependency |
@alexec I think 3.2 we will follow the cherry pick way. after 3.3 onwards we will merge all fixes (appropriates) to patch release instead of pick and choose. |
I will include it
…Sent from my iPhone
On Nov 12, 2021, at 8:04 AM, Valér Orlovský ***@***.***> wrote:
Could you please clarify whether #6905 will be included ? It's in @alexec's list but I don't see it in the new checklist. It's blocking us from trying emissary, so would be nice if possible 🙂
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
|
|
Is it too late to get #6995 in? it's been a couple weeks and it would definitely help me out. |
We don't normally back port features I'm afraid. |
Hi @alexec - This issue is still opened and 3.2.4 has been released. Are the listed items still slated to be included in the next release? |
Please see changelog. |
TestDoNotCreatePodsUnderStopBehavior
fordocker
executor. Fixes Fix flakey TestDoNotCreatePodsUnderStopBehavior on docker #7040 (test: skipTestDoNotCreatePodsUnderStopBehavior
fordocker
executor. Fixes #7040 #7048) 3979f40{{= workflow.creationTimestamp }}
and{{ workflow.creationTimestamp }}
#6906 (feat: support new field - RFC3339 in creationTimeStamp. Fixes #6906 #7044) 0baa4a2The text was updated successfully, but these errors were encountered: