Tyler, thanks for the process document, very helpful:
Here is another type of release challenge:
Database table alteration is a whole additional minefield I am dealing
with. Preservation of existing data and migration of existing data into
the added fields, dealing with 3 database engines,
Great read! Thanks!
As someone on a team that mostly deploys non-Mediawiki code, I appreciate
the mention that this code also exists and does not follow the same process!
Big thanks!
MrG
On Thu, 30 Sept 2021 at 23:06, Tyler Cipriani
wrote:
> On Thu, Sep 30, 2021 at 9:38 AM Christoph Jauera
On Thu, Sep 30, 2021 at 9:38 AM Christoph Jauera <
christoph.jau...@wikimedia.de> wrote:
> I wonder if it makes sense to sneak in the aspect of canary servers.
> Whenever I talk to other devs about our deployment processes they are most
> amazed by that concept.
>
That's a great thought! During
Great, really nice! I like. <3
I wonder if it makes sense to sneak in the aspect of canary servers.
Whenever I talk to other devs about our deployment processes they are most
amazed by that concept.
Am Di., 28. Sept. 2021 um 01:13 Uhr schrieb Aaron Halfaker <
aaron.halfa...@gmail.com>:
> So
So succinct! Great read.
It reads like the Inverted pyramid[1]:
- The gist
- Important details
- The hairy details that you couldn't understand without the gist and
important details
1. https://en.wikipedia.org/wiki/Inverted_pyramid_(journalism)
On Mon, Sep 27, 2021 at 4:04 PM
This is great, thanks Tyler! \o/
On Mon, Sep 27, 2021 at 3:25 PM Tyler Cipriani
wrote:
> Last week, I spoke to a few of my Wikimedia Foundation colleagues about
> how we deploy code—I completely botched it.
>
> At the end of the conversation, I was pretty sure I'd only succeeded in
> making a
