Opened 12 years ago

Closed 7 years ago

#11420 closed enhancement (worksforme)

explain patch basing and pre-releases in Developer's Guide

Reported by: ltw Owned by: mvngu
Priority: minor Milestone: sage-duplicate/invalid/wontfix
Component: documentation Keywords:
Cc: kcrisman, niles 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 kcrisman

Cc: kcrisman added

comment:2 Changed 12 years ago by niles

Cc: niles added

comment:3 Changed 12 years ago by ltw

Type: defectenhancement

comment:4 Changed 9 years ago by jdemeyer

Milestone: sage-5.11sage-5.12

comment:5 Changed 9 years ago by vbraun_spam

Milestone: sage-6.1sage-6.2

comment:6 Changed 9 years ago by vbraun_spam

Milestone: sage-6.2sage-6.3

comment:7 Changed 8 years ago by vbraun_spam

Milestone: sage-6.3sage-6.4

comment:8 Changed 7 years ago by jdemeyer

Milestone: sage-6.4sage-duplicate/invalid/wontfix
Reviewers: Jeroen Demeyer
Status: newneeds_review

In think the git workflow is explained well enough in the developer manual. Especially when using the git trac command, it's easy.

comment:9 Changed 7 years ago by jdemeyer

Status: needs_reviewpositive_review

comment:10 Changed 7 years ago by vbraun

Resolution: worksforme
Status: positive_reviewclosed
Note: See TracTickets for help on using tickets.