Closed benibenj closed 4 months ago
It's really cool that you guys make the planning and execution of vs code development this open and transparent for the community, thank you for that.
I was wondering if the outcome/results of tasks and goals defined in the Iteration Plan are also made public. Sometimes I see things that really interest me but don't get released and I'm always curious about what happened (generally stretch goals, exploration and investigations)
I was wondering if the outcome/results of tasks and goals defined in the Iteration Plan are also made public. Sometimes I see things that really interest me but don't get released and I'm always curious about what happened (generally stretch goals, exploration and investigations)
They should all have issues assigned to them that you can follow along and subscribe to. No further information besides what is in those issues is provided.
They should all have issues assigned to them that you can follow along and subscribe to
I see. Well, often they are assigned issues that are very old feature requests that generally don't get updated unless they are implemented, e.g:
💪 Deep folder settings https://github.com/microsoft/vscode/issues/32693 @sandy081
I'm looking forward for that one but I think it is unlikely that it will be implemented in this iteration. I would really appreciate some more info. The issue is from 2017.
Microsoft recently integrated CleatType Text Tuner support into Chrome/Chromium/Skia. This was released in Chromium 124. Since then, font rendering in Chrome has improved drastically on Windows (especially for small font sizes).
https://chromestatus.com/feature/6236420349100032
Is there a plan to integrate latest Chromium build or at least Chromium 124 in VSCode as well?
Thanks!
this has all been bull I've been honest in all my doings nothing has been corrupted you even now are looking at what I'm typing even posting thinking someone will answer will you know I'm in hospital dying because of this and it appears the only way to cover up your crimes is to kill me off please don't i love my wife more than anything even money so yes end games i don't want anything to do with you guy's ever again wealth is something i have always had and know how to obtain and never have i ever had to kill rob or steal by any means to have it this has been the devices by with the weak has to obtain wealth and positions and power not me Iam greater and above it all a God of Gods worlds without ends eternal without end like your game and like you YOUR TURN WITHOUT MERCEY NOR FORGIVENESS SO LET IT BE WRITTEN SO LET IT BE DONE CURSE I GIVE UNTO YOU ALL IRREVOCALBLE IN TIME AND IN ETERNITIES ,
Monday
verification-needed
oron-testplan
labelTuesday
blocked
and status update comment in the issue.Wednesday
verification-steps-needed
issues @benibenjThursday
insider
build is green @benibenjinsider
builds (includes vscode.dev publishing). The default time is Thursday EOD (Redmond) @benibenjverification-steps-needed
issues @benibenjmain
and release @Iramos15release/<x.y>
release/*
as the VS Code Branch parameter (it's the default so you shouldn't have to change anything)main
is open for business and all issues on the current iteration are candidates and that the candidate release process is to be followed.stable
build from release/<x.y> branch to ensure stable build is green @benibenjpackage.json
onmain
- @benibenjmicrosoft/vscode
repo and ensure that it has a due date. The created milestone and its due date will be automatically synced across our repos. @benibenjFriday
candidate
fixes should be made for major bugs only - to be discussed in stand-up meeting and approvedcandidate
PRs should find testers to test merged candidates. VS Code candidates should be tested on newly released Insiders.Friday/Monday
Monday - Wednesday
release/<x.y>
, and close open candidate issues that have already been merged to the release branch. @Iramos15Insider
fromrelease/<x.y>
(roughly on a daily basis) @Iramos15Insider
@Iramos15candidate
PRs should find testers to test merged candidates. VS Code candidates should be tested on newly released Insiders. teamscripts/test-documentation.sh|bat
after compiling the vscode repo, and fix any issues regarding new undocumented colors. Changes made to the vscode-docs repository must be merged to the main branch of that repository for the script to acknowledge them. False positives within thecolor
section invscode-known-variables.json
can be moved under theothers
section of that file. @Iramos15Wednesday/Thursday - Expected release day (this may change)
main
for all platforms @Iramos15release/x.y
for theprod
deployment target. Note that there are four deploy approvals needed - one for overall and one per each of the three service regions @Iramos15git tag <x.y.z>
git push origin <x.y.z>
... > Create Release
. Use the correct title and description from our release notes. Also change the relative links for the key highlight list items to absolute links Exampleinsider
builds @Iramos15main
@Iramos15