Opened 12 years ago
Closed 7 years ago
#11420 closed enhancement (worksforme)
explain patch basing and pre-releases in Developer's Guide
| Reported by: | Kelvin Li | Owned by: | Minh Van Nguyen |
|---|---|---|---|
| Priority: | minor | Milestone: | sage-duplicate/invalid/wontfix |
| Component: | documentation | Keywords: | |
| Cc: | Karl-Dieter Crisman, Niles Johnson | Merged in: | |
| Authors: | Reviewers: | Jeroen Demeyer | |
| Report Upstream: | N/A | Work issues: | |
| Branch: | Commit: | ||
| Dependencies: | Stopgaps: |
Status badges
Description
The Developer's Guide does not mention pre-releases, where to get them, where they are announced, how they should be used (e.g. to be used as bases for patches and for testing), or suggested workflows.
Inspired by http://ask.sagemath.org/question/567/on-what-versions-should-trac-patches-be-based
Change History (10)
comment:1 Changed 12 years ago by
| Cc: | Karl-Dieter Crisman added |
|---|
comment:2 Changed 12 years ago by
| Cc: | Niles Johnson added |
|---|
comment:3 Changed 12 years ago by
| Type: | defect → enhancement |
|---|
comment:4 Changed 9 years ago by
| Milestone: | sage-5.11 → sage-5.12 |
|---|
comment:5 Changed 9 years ago by
| Milestone: | sage-6.1 → sage-6.2 |
|---|
comment:6 Changed 9 years ago by
| Milestone: | sage-6.2 → sage-6.3 |
|---|
comment:7 Changed 8 years ago by
| Milestone: | sage-6.3 → sage-6.4 |
|---|
comment:8 Changed 7 years ago by
| Milestone: | sage-6.4 → sage-duplicate/invalid/wontfix |
|---|---|
| Reviewers: | → Jeroen Demeyer |
| Status: | new → needs_review |
comment:9 Changed 7 years ago by
| Status: | needs_review → positive_review |
|---|
comment:10 Changed 7 years ago by
| Resolution: | → worksforme |
|---|---|
| Status: | positive_review → closed |
Note: See
TracTickets for help on using
tickets.
In think the git workflow is explained well enough in the developer manual. Especially when using the
git traccommand, it's easy.