| Fjalapeno added a subscriber: Anomie. Fjalapeno added a comment. |
In T197616#4409174, @greg wrote:(if it blocks then it should be a sub-task of the SDC deployment, not the other way around, right? ;) )
@CCicalese_WMF can you make sure the task tree is correct here?
In T197616#4445656, @greg wrote:Additional question: how would this test commons receive sufficient traffic to expose any potential issues?
@Anomie I believe you have some thoughts here… can you provide some info for @greg?
In T197616#4409248, @greg wrote:High because due by end of August (and summer is busy).
@greg Just to confirm, yes we need this end of august.
In T197616#4429492, @Krinkle wrote:In T197616#4297600, @daniel wrote:The beta setup is probably not going to cover all the angles for e.g. wikibase change propagation.
@Krinkle Can you clarify what angles you think aren't going to covered and why they may be important. Also please say whether each angle is a blocker or not in your opinion.
I don't know the internals of Wikibase changeprop, but if it is a blocker to gaining confidence in SDC testing, it is probably also significant for general testing in Beta Cluster. Continued absence of it, would decrease value of overall QA efforts, and the efforts from other teams currently operating their services in Beta Cluster.
Task description:Database: testcommonswiki
Config: as similar to commonswiki as possibleI think we should formally recognise this as technical debt, and plan for it accordingly. Manually maintaining this set-up of another wiki inside prod will require effort, and probably also from other teams at unexpected times. I don't think we can guarantee it will always be in sync, and never cause issues with something else in prod?
If we do go this route, I'd recommend setting a deadline to delete the wiki (e.g. after 6 months, or 12 months).
Note that between prod and beta, settings and conditionals for commonswiki are naturally in sync.
In T197616#4448548, @greg wrote:Setting back to To Triage until we clarify use cases (the above questions from Timo and I).
@Krinkle can you provide some questions that we need to answer in regards to the above. I think we are having trouble doing anything actionable here because it isn't clear what we need to answer or turn into tickets baed on your feedback. Since @greg is saying your concerns a blocker to triaging this task, I want to make sure we have your needs clearly defined so we can move forward. (Sorry for being pedantic, but just want to make sure we understand fully what is being asked since we are on a deadline - thanks for taking the time to provide this info)
Cc: Anomie, Krinkle, Liuxinyu970226, Jdforrester-WMF, Fjalapeno, Abit, Aklapper, greg, Reedy, CCicalese_WMF, daniel, Lahi, PDrouin-WMF, Gq86, E1presidente, JunaidHafeez, Ramsey-WMF, Cparle, BJ6123C7BTD, Anooprao, SandraF_WMF, GoranSMilovanovic, Jayprakash12345, QZanden, Tramullas, Acer, Zoranzoki21, LawExplorer, DatGuy, Devwaker, Niklitov, Urbanecm, Liudvikas, JEumerus, StevenJ81, Susannaanas, Tulsi_Bhagat, Wong128hk, Luke081515, SimmeD, Aschroet, Jane023, Wikidata-bugs, Snowolf, Base, matthiasmullie, aude, Dcljr, Ebe123, Koavf, Ricordisamoa, Lydia_Pintscher, Fabrice_Florin, Raymond, zeljkofilipin, Rschen7754, Steinsplitter, Matanya, Mbch331, Rxy, Jay8g, Krenair
_______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
