#15580: Integrate prereq in the new build system
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-6.1
Component: distribution | Resolution:
Keywords: | Merged in:
Authors: R. Andrew Ohana, | Reviewers: R. Andrew Ohana
Jeroen Demeyer | Work issues:
Report Upstream: N/A | Commit:
Branch: | 19d5a15ba83c7861237be766420541bb783ec34f
u/jdemeyer/ticket/15580 | Stopgaps:
Dependencies: #15596 |
-------------------------------------+-------------------------------------
Comment (by jdemeyer):
Replying to [comment:52 vbraun]:
> I want to have a workflow where I merge branches, test, and once it
works slap on the new version and release. Bumping the version should not
require another test run. Bumping the version just to make the new
configure-x.y.z tarball and then resetting to before the version bump is
also not desirable.
Why not the following workflow:
1. In volker's private repo, bump the version number and merge various
patches
2. Run `sage --sdist` to generate the configure tarball
3. Put the configure tarball in some accessible place
4. Run the buildbots on Volker's private repo
5. If tests pass, merge Volker's repo with the official repo.
(Ideally, I would argue there should also be a 4b. Run at least one
buildbot on the source tarball instead of the git repo)
What alternative would you propose? You need to generate the configure
tarball anyway before you can test it, regardless of any version bumps...
--
Ticket URL: <http://trac.sagemath.org/ticket/15580#comment:53>
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/groups/opt_out.
