Coordination of the two workstations: split, state and shared decisions
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 1/5
- Tempo stimato
- Meno di un'ora
- Idoneità per principianti
- 1/100
- Tipo di issue
- Documentazione
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- csharp, github-actions
- Ambito
- developer-experience
Direzione di ricerca
This issue is a live coordination board for two workstations, with work split, current state, shared decisions, and known flaky tests. Read the relevant section and its comments before acting; it does not define a standalone change or a completion criterion, so it is not suitable as a first contribution.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Two workstations work on the repository at the same time. This issue is their shared board: who owns what, what is in flight, and the decisions both must follow. Each side edits its own section and adds a comment when something the other side should know changes.
Split
Workstation A: the admin. Milestones A4 to A7, everything under admin/, the branches feature/a*, the CI workflow files, and bundles 14 and 15 of the backlog bundles. Also #3263 and #3269, already in work.
Workstation B: the backend backlog. Bundles 1 to 13, 16 and 17, each one pull request into main.
Neither side changes files of the other's area. What one side needs from the other is filed as an issue and named in a comment here.
State of A (20 Nov 2026)
- Merged into
main: A4 (#3375), A5 (#3405, 034616ae), #3351 (#3269), #3357 (#3263), #3359 (bundle 14), #3394 (#3314), #3413, #3415, #3374 (TypeScript 7, a1d08b54). - A6 (#3431) on
feature/a6, cut frommainat b8c246dc: A-51 (#3429) in work, first and alone. Then A-31, A-33, A-34; A-32, A-36, A-38; A-52, A-40, A-35; A-37, A-39. No model change, nothing undersrc/planned. - Beside it, into
main: #3403 in work. Waiting for a free lane: #3354 (after A-51), #3395, #3213, the open items of #3178, #3215, row 3 of #3311 and of #3312. - Asked of B: #3417 and #3418 (A6), #3432 (preview template in the schema, for #3403). None blocks.
- Next: A7 (A-41 to A-47), planned when A6 is under way.
State of B (20 Nov 2026)
- Merged: bundle 1 (#3363, b8c246dc), bundle 2 (#3396, 5849d126 and #3384, 90752c6b), bundle 3 (#3358, b70e17d5), bundle 4 (#3360, d78344ad), bundle 5 (#3362, 4c41a2df), bundle 6 (#3387, 060cc308 and #3388, 6255a82e), bundle 7 (#3389, 8f8f2335), bundle 8 (#3402, d15959b2), bundle 9 (#3404, fbfe9962 and #3406, 0e19ba24). Model changes: bundle 4 (one index in the webhooks
Initial) and #3406 (three indexes in the coreInitial). - The hold is lifted (20 Nov 2026). B also owns bundles 18 to 24 of the triage.
- Open from B: #3433 (bundle 20: #3379, #3364) and #3434 (bundle 19: #3361, #3397, #3399), both in fix rounds after review, no model change; #3440 (#3417, the route
GET /permissions/row-rules), in review, no model change; #3439 (#3418), which holds the model slot: one column,principal_nameoncms_ai_usage, folded into the AI assist plugin's ownInitial. - In work, no pull request yet: bundle 18 (#3372, #3371, #3378, #3373, #3381; it changes the account page's two-factor enrolment under
admin/). - Queue after them: #3391 (after bundle 18); bundle 12 (media, then search); 10; 11; 13; 23; 21; 22; 16; 24; 25 (#3435, #3436); 26 (#3441, #3442); 17; then the notes of
1.0.0-preview.2. - Model changes to come, one at a time and announced here first: #3308, then #3265 if it needs one, then #3411, then #3373 if it takes a constraint.
- Changes B made in A's area on the maintainer's word: #3377 (two admin test files, in #3363) and #3386 (two lines in
compose.yml, in #3388). - Filed by B: #3361, #3364, #3377, #3379, #3380, #3381, #3385, #3386, #3391, #3392, #3393, #3397, #3399, #3408, #3409, #3410, #3411, #3435, #3436, #3441, #3442.
Decisions both sides follow
- No new migration: model changes fold into the
Initialbaseline. Only one open pull request may change the model at a time, on either side. Say so here before opening one. A has none planned in A4 or A5. - Merge by hand after reading every check on the last commit, the ones that are not required too (
End-to-end (admin),Image, the SQL Server data jobs). No auto-merge: #3350 merged one minute before its fix for a failingImagecheck arrived. - After a merge into
main, read the push run before reporting. A redmainis the first item of the queue for the side whose merge it was. - Local test runs are kept minimal (the build, the touched test projects, each new test once); CI covers the rest. A failed job that looks like a timing flake is rerun once, and fixed only if it repeats.
- The size budget of the admin's first download is 3,600,000 B since #3353; #3354 looks for savings.
ci.ymlis not dispatched by hand for a pull request intomain. Both sides share the limit of concurrent CI jobs and the API rate limit: one watcher per run, with--interval 60.
Known flaky tests
MediaAssetPanelTestsofFluentCMS.Plugins.Media.Admin.Tests: a wait that times out when the thread pool is starved on a loaded runner. Rerun.ReferenceChecksAreBoundedWhateverTheNumberOfReferencesofFluentCMS.Data.Tests: failed once on SQL Server 2025 under load, not since.- #3209: the rate limit test on the Windows runner.
- Lingua principale
- C#
- Stelle
- 567
- Fork
- 107
- Merge medio
- 1h 19m
- PR unite (30g)
- 353
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di fluentcms/FluentCMS
-
area:localization plugin type:bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
area:storage type:bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
I maintainer di solito rispondono entro 1 giorno
-
area:testing type:bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
area:api area:publishing type:feature
Difficoltà 4/5 3-5 giorni Idoneità per principianti 55/100
fluentcms/FluentCMS#3473 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
area:storage plugin type:bug
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di fluentcms/FluentCMS
Issue simili
-
worldInstancedOccluderNode reads its appendix count as one byte, but it is a VLQForse già presa @spuddeh l’ha presa oggi. Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
fix(ocr): compile the Tesseract-free pipeline with Tokio runtimeForse già presa @Goldziher l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
priority:P2
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
-
lompotc silently drops Java/C# class members past 128 instead of erroring, as its header claimsApertabug sev-5 vm
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100