#19565: develop manual : use develop instead of master
-------------------------+-------------------------------------------------
Reporter: | Owner:
chapoton | Status: needs_review
Type: | Milestone: sage-6.10
defect | Resolution:
Priority: major | Merged in:
Component: | Reviewers: Travis Scrimshaw
documentation | Work issues:
Keywords: | Commit:
Authors: | d52a6bf3dae91fb4f42be8ae7656844ae83c4c7e
Frédéric Chapoton | Stopgaps:
Report Upstream: N/A |
Branch: |
public/19565 |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by tscrim):
What do other projects do for their latest beta branch versus stable
release? I thought `master` was suppose to be used for stable versions.
Granted, our beta versions are usually fairly stable, but even once in
awhile, we do break things badly with beta versions...
Actually, a somewhat radical thought, what if we do make `master` somehow
be the more granular bumps and not call them betas but, e.g., `6.10.4`,
and then we have a latest merged branch that Volker includes? This way we
could stop with those "wait until next beta to deal with
conflicts/problems" messages for closed tickets that Volker has already
included but not released.
--
Ticket URL: <http://trac.sagemath.org/ticket/19565#comment:6>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
