941028e705
- Add release-gate.yml: 11-job pipeline (lint, tests, Docker build/smoke, Trivy scan, dep audit, audit checks, e2e API+UI, PR summary comment) - Fix CI double-trigger on release branches (push + PR) - Add CODE_OF_CONDUCT.md, SECURITY.md, PR template - Add docs: git-workflow, architecture (ADR), release, operations, community - Add profiles/fastapi-vue for automated audit checks - Add docs/PROCESSES.md: index of 19 available processes
44 lines
1 KiB
Markdown
44 lines
1 KiB
Markdown
# Roadmap — Docling Studio
|
|
|
|
Last updated: YYYY-MM-DD
|
|
|
|
## Now (current release cycle)
|
|
|
|
<!-- Features actively being worked on -->
|
|
|
|
| Feature | Issue | Status |
|
|
|---------|-------|--------|
|
|
| ... | #NNN | In progress |
|
|
|
|
## Next (next release cycle)
|
|
|
|
<!-- Planned for the next release, prioritized -->
|
|
|
|
| Feature | Issue | Priority |
|
|
|---------|-------|----------|
|
|
| ... | #NNN | P1 |
|
|
|
|
## Later (future, no timeline)
|
|
|
|
<!-- Ideas accepted but not yet scheduled -->
|
|
|
|
| Feature | Issue |
|
|
|---------|-------|
|
|
| ... | #NNN |
|
|
|
|
## Not Planned
|
|
|
|
<!-- Explicitly declined or out of scope — explaining why avoids repeat requests -->
|
|
|
|
| Feature | Reason |
|
|
|---------|--------|
|
|
| ... | ... |
|
|
|
|
---
|
|
|
|
## How to Propose a Feature
|
|
|
|
1. Check [existing issues](https://github.com/scub-france/Docling-Studio/issues) — it may already be tracked
|
|
2. Open a new issue using the **Feature** template
|
|
3. If it's a significant change, consider writing an [ADR](../architecture/adr-guide.md)
|
|
4. The maintainers will triage and prioritize (see [issue triage](issue-triage-process.md))
|