Release: qualify Turian 4 with .NET 11 Android export and audio

Abierto
#366 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
android, csharp

Línea de trabajo

Start by reading related issues #61, #254, #255, #257, #259, #269, #271, #273, #274, and #275, then identify the release and CI entry points for the .NET 11 Android workflow. The issue calls for broad release qualification across desktop, Android, audio, signing, diagnostics, migration notes, and announcement evidence, with several checks dependent on an owner decision. Done means recording reproducible results with exact revisions, toolchains, artifacts, and limitations; publication remains an explicit owner action.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

p:high t:feature

Current State

The next major release combines .NET 11 Android export with basic audio and a reproducible supported workflow.

Tasks

  • Pin final SDK/workload/toolchain versions and validate the release candidate in CI, on the supported device and emulator.
  • Qualify export/install, touch/UI, in-place content, lifecycle, signing/AAB, ABI/alignment and diagnostics.
  • Require audio in editor and exports, silent headless execution and repeated-session cleanup; verify Android playback/backend compatibility explicitly.
  • Prepare v4 migration/release notes and reviewable Turian and MASS4 announcement drafts, captures and links using public sample content only.
  • Verify competitive statements before publication; do not assert industry-first status without evidence.
  • Record the final dotnet-11-to-main merge method after owner decision; prepare artifacts without publishing automatically.

Acceptance Criteria

  • Evidence identifies exact revisions/toolchains/artifacts and limitations; desktop and Android checks pass.
  • Announcement distinguishes CoreCLR from NativeAOT and states tested platform support.
  • Tags, publication, blogs and store submission remain explicit owner actions.

Related

  • #61, #254, #255, #257, #259, #269, #271, #273, #274, #275.
Lenguaje dominante
C#
Estrellas
1
Forks
1
Merge medio
1 h 58 min
PR fusionados (30 d)
28

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de MASS4ORG/Turian

Todos los issues de MASS4ORG/Turian

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.