Hello everyone,
Until today if you wanted to get a backport or config change deployed to production you used what was termed the "SWAT" window.
As of today that window of time is now called the "Backport and Config" window. This solves a few problems. First, the overly militarized and violence-implying name is no longer something we want in our community. Second, this now accurately and clearly describes what the purpose of the window is.
This should now be changed everywhere including the Deployment Calendar[0], but if you see any errant mentions of it in documentation, please feel free to update it (WP:BOLD) or contact the Wikimedia Release Engineering Team.
Thank you,
Greg
[0] https://wikitech.wikimedia.org/wiki/Deployments
I was literally just thinking of this! Glad to hear it, for exactly the reasons you said. Go team. :)
On Mon, Jun 8, 2020 at 9:57 AM Greg Grossmeier greg@wikimedia.org wrote:
Hello everyone,
Until today if you wanted to get a backport or config change deployed to production you used what was termed the "SWAT" window.
As of today that window of time is now called the "Backport and Config" window. This solves a few problems. First, the overly militarized and violence-implying name is no longer something we want in our community. Second, this now accurately and clearly describes what the purpose of the window is.
This should now be changed everywhere including the Deployment Calendar[0], but if you see any errant mentions of it in documentation, please feel free to update it (WP:BOLD) or contact the Wikimedia Release Engineering Team.
Thank you,
Greg
[0] https://wikitech.wikimedia.org/wiki/Deployments
-- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
I think we need some shorter version to refer to this window. New name is cool, but swat is shorter.
Martin
On Tue, Jun 9, 2020, 5:17 PM Max Binder mbinder@wikimedia.org wrote:
I was literally just thinking of this! Glad to hear it, for exactly the reasons you said. Go team. :)
On Mon, Jun 8, 2020 at 9:57 AM Greg Grossmeier greg@wikimedia.org wrote:
Hello everyone,
Until today if you wanted to get a backport or config change deployed to production you used what was termed the "SWAT" window.
As of today that window of time is now called the "Backport and Config" window. This solves a few problems. First, the overly militarized and violence-implying name is no longer something we want in our community. Second, this now accurately and clearly describes what the purpose of the window is.
This should now be changed everywhere including the Deployment Calendar[0], but if you see any errant mentions of it in documentation, please feel free to update it (WP:BOLD) or contact the Wikimedia Release Engineering Team.
Thank you,
Greg
[0] https://wikitech.wikimedia.org/wiki/Deployments
-- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
Ops mailing list Ops@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ops
hmm, What about B&C? Similar when we call "Trust and Safety" as "T&S"
On Tue, Jun 9, 2020 at 11:26 PM Martin Urbanec martin.urbanec@wikimedia.cz wrote:
I think we need some shorter version to refer to this window. New name is cool, but swat is shorter.
Martin
On Tue, Jun 9, 2020, 5:17 PM Max Binder mbinder@wikimedia.org wrote:
I was literally just thinking of this! Glad to hear it, for exactly the reasons you said. Go team. :)
On Mon, Jun 8, 2020 at 9:57 AM Greg Grossmeier greg@wikimedia.org wrote:
Hello everyone,
Until today if you wanted to get a backport or config change deployed to production you used what was termed the "SWAT" window.
As of today that window of time is now called the "Backport and Config" window. This solves a few problems. First, the overly militarized and violence-implying name is no longer something we want in our community. Second, this now accurately and clearly describes what the purpose of the window is.
This should now be changed everywhere including the Deployment Calendar[0], but if you see any errant mentions of it in documentation, please feel free to update it (WP:BOLD) or contact the Wikimedia Release Engineering Team.
Thank you,
Greg
[0] https://wikitech.wikimedia.org/wiki/Deployments
-- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
Ops mailing list Ops@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ops
Ops mailing list Ops@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ops
We could go the SuSa route and call it the BACON window, for BAckports and CONfigs
On Tue, Jun 9, 2020 at 5:29 PM Amir Sarabadani ladsgroup@gmail.com wrote:
hmm, What about B&C? Similar when we call "Trust and Safety" as "T&S"
On Tue, Jun 9, 2020 at 11:26 PM Martin Urbanec martin.urbanec@wikimedia.cz wrote:
I think we need some shorter version to refer to this window. New name is cool, but swat is shorter.
Martin
On Tue, Jun 9, 2020, 5:17 PM Max Binder mbinder@wikimedia.org wrote:
I was literally just thinking of this! Glad to hear it, for exactly the reasons you said. Go team. :)
On Mon, Jun 8, 2020 at 9:57 AM Greg Grossmeier greg@wikimedia.org wrote:
Hello everyone,
Until today if you wanted to get a backport or config change deployed to production you used what was termed the "SWAT" window.
As of today that window of time is now called the "Backport and Config" window. This solves a few problems. First, the overly militarized and violence-implying name is no longer something we want in our community. Second, this now accurately and clearly describes what the purpose of the window is.
This should now be changed everywhere including the Deployment Calendar[0], but if you see any errant mentions of it in documentation, please feel free to update it (WP:BOLD) or contact the Wikimedia Release Engineering Team.
Thank you,
Greg
[0] https://wikitech.wikimedia.org/wiki/Deployments
-- | Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E | | Dir. Engineering Productivity A18D 1138 8E47 FAC8 1C7D |
Ops mailing list Ops@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ops
Ops mailing list Ops@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ops
-- Amir (he/him) _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Tue, Jun 9, 2020 at 3:33 PM AntiCompositeNumber anticompositenumber@gmail.com wrote:
We could go the SuSa route and call it the BACON window, for BAckports and CONfigs
$ scap say "Scappy approves of BACON as the window name" ------------------------------------------------ / \ | Scappy approves of BACON as the window name | \ / ------------------------------------------------ \ \ \ ___ ____ ⎛ ⎛ ,---- \ //==--' _//|,.·//==--' ____________________________ _OO≣=- ︶ ᴹw ⎞_§ ______ ___\ ___\ ,__ / __ \ (∞)_, ) ( | ______/__ / /__ / /_/ / /_/ / ¨--¨|| |- ( / __________/ ___/ __^_/ .__/ ««_/ «_/ jgs/bd808 /_/
Bryan
On Wed, 17 Jun 2020 at 16:14, Jeremy Baron jeremy@tuxmachine.com wrote:
or BCC or BACC window.
BACC sounds good to me: it's easy to pronounce. BCC already has a meaning.
Other suggestion: This is the "fast travel" route in comparison to the regular weekly trains, therefore the short name could play with that idea. "Beam" would be quite expressive, IMO:
"Beam up the patches, Scotty!" Excuse my nerding... ;-)
Demian (aka. Aron)
"Beam" sounds great!
Alternatively, how about the more mundane "fast track" or "express deploy", which fits the with image of "train"?
Am 17.06.20 um 16:25 schrieb Aron Manning:
On Wed, 17 Jun 2020 at 16:14, Jeremy Baron jeremy@tuxmachine.com wrote:
or BCC or BACC window.
BACC sounds good to me: it's easy to pronounce. BCC already has a meaning.
Other suggestion: This is the "fast travel" route in comparison to the regular weekly trains, therefore the short name could play with that idea. "Beam" would be quite expressive, IMO:
"Beam up the patches, Scotty!" Excuse my nerding... ;-)
Demian (aka. Aron) _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On Mon, 8 Jun 2020 at 17:58, Greg Grossmeier greg@wikimedia.org wrote:
Until today if you wanted to get a backport or config change deployed to production you used what was termed the "SWAT" window.
As of today that window of time is now called the "Backport and Config" window. This solves a few problems. First, the overly militarized and violence-implying name is no longer something we want in our community. Second, this now accurately and clearly describes what the purpose of the window is.
A good change. Thanks!
Dan
However, it takes about five times as long to say or type as before, and it is much more unspecific. I think this might be reason for problems.
Best regards,
MGC
On 17.06.20 13:54, Dan Garry (Deskana) wrote:
On Mon, 8 Jun 2020 at 17:58, Greg Grossmeiergreg@wikimedia.org wrote:
Until today if you wanted to get a backport or config change deployed to production you used what was termed the "SWAT" window.
As of today that window of time is now called the "Backport and Config" window. This solves a few problems. First, the overly militarized and violence-implying name is no longer something we want in our community. Second, this now accurately and clearly describes what the purpose of the window is.
A good change. Thanks!
Dan _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
I don't think we have the same idea of what the word "unspecific" means. From my perspective – as a German native speaker who only knows the abbreviation "SWAT" from bad TV series, and didn't even know what it means until I looked it up recently – we could have it named "lemon" as well, and that would not be more unspecific than "SWAT". I'm happy it's gone. Now let's move on and do something that actually makes a difference. The planet is still burning, after all.
Kind regards Thiemo
Yeah, this is an excellent change.
On Wed, Jun 17, 2020 at 8:47 AM Thiemo Kreuz thiemo.kreuz@wikimedia.de wrote:
I don't think we have the same idea of what the word "unspecific" means. From my perspective – as a German native speaker who only knows the abbreviation "SWAT" from bad TV series, and didn't even know what it means until I looked it up recently – we could have it named "lemon" as well, and that would not be more unspecific than "SWAT". I'm happy it's gone. Now let's move on and do something that actually makes a difference. The planet is still burning, after all.
Kind regards Thiemo
Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
wikitech-l@lists.wikimedia.org