purescript / purescript/trypurescript
Create a dedicated development & release guide
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- PureScript
- Sterne
- 121
- Forks
- 51
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
As discussed in #218, I think we ought to split out the development instructions for Try PureScript from the main README, and we should expand those instructions to include cutting new releases of the project.
The development instructions should cover what they already do: how to set up the local server, how to set up the local client, and how to update the packages and package set.
The release instructions could include things not currently described, including:
- Updating the hardcoded tag used for examples
- How to check that the externs for an upgraded package set don't overwhelm the server
- How to run a deployment
and ideally this could be aggregated in checklist form, so someone who wants to make a release can move step-by-step through the instructions from a fresh clone of the repository.
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Start with the main README and the discussion in #218, then trace the existing instructions for setting up the local server and client and updating packages and the package set. Done means a dedicated guide with a fresh-clone checklist covering those development steps plus tag updates, externs checks, and deployment.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Bereich
- documentation, release
- Issue-Typ
- Dokumentation
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 42/100