Opened 10 years ago

Closed 5 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:

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 10 years ago by kcrisman

  • Cc kcrisman added

comment:2 Changed 10 years ago by niles

  • Cc niles added

comment:3 Changed 10 years ago by ltw

  • Type changed from defect to enhancement

comment:4 Changed 7 years ago by jdemeyer

  • Milestone changed from sage-5.11 to sage-5.12

comment:5 Changed 7 years ago by vbraun_spam

  • Milestone changed from sage-6.1 to sage-6.2

comment:6 Changed 7 years ago by vbraun_spam

  • Milestone changed from sage-6.2 to sage-6.3

comment:7 Changed 6 years ago by vbraun_spam

  • Milestone changed from sage-6.3 to sage-6.4

comment:8 Changed 5 years ago by jdemeyer

  • Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix
  • Reviewers set to Jeroen Demeyer
  • Status changed from new to needs_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 5 years ago by jdemeyer

  • Status changed from needs_review to positive_review

comment:10 Changed 5 years ago by vbraun

  • Resolution set to worksforme
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.