Change Details

In this task, let's clarify how temp accounts deployment will impact the release train. In Q3 2024, we aim to deploy temp accounts on testwiki (and loginwiki, metawiki). More wikis would follow in Q4. That would mean, for a period of some weeks/months, that testwiki reflects an editing paradigm for anonymous users (temp accounts in place of IP accounts) that is different from the bulk of our production wikis. Does that present a concern to #release-engineering-team? One thought is that we encourage WMF teams and QA folks to verify their changes on both testwiki (temp accounts) and testwiki2 (IP editing, as it exists today), to avoid any surprises.

In this task, let's clarify how temp accounts deployment will impact the release train. In Q3 2024, we aim to deploy temp accounts on testwiki (and loginwiki, metawiki). More wikis would follow in Q4. That would mean, for a period of some weeks/months, that testwiki reflects an editing paradigm for anonymous users (temp accounts in place of IP accounts) that is different from the bulk of our production wikis. Does that present a concern to #release-engineering-team? One thought is that we encourage WMF teams and QA folks to verify their changes on both testwiki (temp accounts) and testwiki2 (IP editing, as it exists today), to avoid any surprises. Related: {T355880}

In this task, let's clarify how temp accounts deployment will impact the release train. In Q3 2024, we aim to deploy temp accounts on testwiki (and loginwiki, metawiki). More wikis would follow in Q4. That would mean, for a period of some weeks/months, that testwiki reflects an editing paradigm for anonymous users (temp accounts in place of IP accounts) that is different from the bulk of our production wikis. Does that present a concern to #release-engineering-team? One thought is that we encourage WMF teams and QA folks to verify their changes on both testwiki (temp accounts) and testwiki2 (IP editing, as it exists today), to avoid any surprises. Related: {T355880}