ClickHouse / ClickHouse/clickhouse-java
[repo] Create Pre-release workflow or find point where release verification should happen
- Vorherrschende Sprache
- Java
- Sterne
- 1.6k
- Forks
- 636
- Ø Merge
- 2 T. 23 Std.
- Gemergte PRs (30 T.)
- 29
Beschreibung
## Description
Client is the core library for many connectors. If we release a breaking change unnoticed it may require more effort to fix late. Today we have a release workflow that publishes to Maven. But we should not block this by tests.
What should be done:
- Evaluate idea of creating pre-release wf that can be used to trigger verification tests.
- Find out what to do with long running test WF's in other repos. How they would deliver result to java client maintainers.
- Research what can be done for community users to have similar signal for tests.
Beitragsleitfaden
Rechercherichtung
Start by reviewing the existing release workflow that publishes to Maven and identify where verification currently occurs. Then examine the long-running test workflows in other repositories and how their results could reach Java client maintainers and community users. Done means a decided pre-release verification approach and a clear result-delivery plan.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- github-actions, java
- Bereich
- ci-cd, release, testing
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Ruhig
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 35/100