That would be useful.
The current script we use is
https://github.com/sympy/sympy/blob/master/release/fabfile.py. It
doesn't handle changelog (except for the authors section), but it does
just about everything else. It runs everything in a Vagrant machine,
and it handles running the tests, (taggin
Hello All,
FWIW, we have a release script for xonsh that handles many elements of a
release (tagging, changelog, building and deploying docs, pypi conda-forge,
etc. ): https://github.com/xonsh/xonsh/blob/master/release.xsh It requires
only minimal, metadata changes to use on other projects. I have
Hi Robert,
On Tue, Jan 24, 2017 at 8:43 AM, wrote:
> FYI, I found more details on how GitLab currently proceeds (and reasons why)
> at
> https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/changelog.md
> .
>
> (You could have a Python equivalent of their bin/changelog tool.)
Th
FYI, I found more details on how GitLab currently proceeds (and reasons
why) at
https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/changelog.md
.
(You could have a Python equivalent of their bin/changelog tool.)
--
You received this message because you are subscribed to the Go
On Thursday, January 12, 2017 at 6:45:00 PM UTC+1, Aaron Meurer wrote:
>
> So how do they [Pandas] deal with merge conflicts in the file? I don't
> want
> people to constantly be having to fix their branches because the
> release notes file has conflicts from another merge.
>
Vladimir Kiselev
>
> So how do they deal with merge conflicts in the file? I don't want
> people to constantly be having to fix their branches because the
> release notes file has conflicts from another merge.
I don't know whether there is a good way to deal with this problem(merge
conflicts). I think " bug
So how do they deal with merge conflicts in the file? I don't want
people to constantly be having to fix their branches because the
release notes file has conflicts from another merge.
Aaron Meurer
On Thu, Jan 12, 2017 at 8:57 AM, Shekhar Prasad Rajak
wrote:
> The
> Files(https://github.com/pand
The Files(
https://github.com/pandas-dev/pandas/tree/master/doc/source/whatsnew) are
written by hand with the PR. Means whenever a bug is fixed PR author must
add the testcase for the bug, and also update the file. Similarly whenever
anything new features implemented.
See this PR :
https://gi
Same topic came up on sage-devel today with a solution.
https://groups.google.com/forum/m/#!topic/sage-devel/81qsOpoOKMM
Isuru Fernando
On Jan 12, 2017 5:30 AM, "Aaron Meurer" wrote:
> So let's figure out how they do it. Does someone do it by hand, or do
> they just deal with the conflicts so
So let's figure out how they do it. Does someone do it by hand, or do
they just deal with the conflicts somehow?
I'm +1 to doing this somehow, because the current process isn't
working. We either need a process wherein everyone updates the release
notes with their pull requests (has to be done at
SciPy does it too: https://github.com/scipy/scipy/tree/master/doc/release
and the notes seem quite comprehensive and well organized.
To avoid merge conflicts we could require a single file for each item in
the notes to be added and then a script compiles the full note set from
those.
Jason
moore
Do you know how pandas generates those files? Are they generated
programmatically or by hand? Usually having a single file for release
notes gets to be a nightmare because of the merge conflicts.
Aaron Meurer
On Wed, Jan 11, 2017 at 1:46 AM, Shekhar Prasad Rajak
wrote:
> I think, it will be easy
I think, it will be easy during the new release to see the changes in one
file, if we add a file in SymPy repo and keep updating it whenever
something added/modified (Before merging PR). Something like this :
https://github.com/pandas-dev/pandas/tree/master/doc/source/whatsnew
--
Shekhar
On Mo
I put them on the release milestone.
Aaron Meurer
On Wed, Jan 4, 2017 at 9:40 PM, Shekhar Prasad Rajak
wrote:
> Hello,
>
> I am trying to complete these PRs :
>
> 1. https://github.com/sympy/sympy/pull/11234
> 2. https://github.com/sympy/sympy/pull/12011
>
> --
> Shekhar
>
> On Monday, 26 Septem
Hello,
I am trying to complete these PRs :
1. https://github.com/sympy/sympy/pull/11234
2. https://github.com/sympy/sympy/pull/12011
--
Shekhar
On Monday, 26 September 2016 22:43:16 UTC+5:30, Aaron Meurer wrote:
>
> Now that GSoC has wrapped up, we should start looking at doing a release.
> A
> How long will it be until the solvers are in a 1.0 ready state,
especially now that GSoC is over?
This can take some time. Since the solveset is not complete with respect to
old `solve`,
one of the things that can be done for faster release of 1.0 is rename
`solveset` as
`solve` and the prev
The current plan is not to deprecate the old assumptions syntax, but to
allow both. In fact, in master, ask(Q.real(x)) will call x.is_real (it also
calls some other stuff too, so it should be at least as smart), so you can
start migrating to the new assumptions syntax. The reverse doesn't work yet
OK, I have created a release branch for 0.7.6.1, which is just 0.7.6 plus
the IPython fixes https://github.com/sympy/sympy/pull/9883. Are there any
other fixes needed for IPython? I tested the notebook in the release branch
and the MathJax printing works.
Otherwise, I will probably push this out l
I think there are already some breaking changes in master, no? Maybe we
should just do a bugfix 0.7.7 release to fix the Jupyter stuff.
Aaron Meurer
On Tue, Sep 1, 2015 at 2:45 AM, Francesco Bonazzi
wrote:
>
>
> On Tuesday, 1 September 2015 06:30:20 UTC+2, AMiT Kumar wrote:
>>
>>
>> Also we hav
On Tuesday, 1 September 2015 06:30:20 UTC+2, AMiT Kumar wrote:
>
>
> Also we have yet not settled with a single assumption system.
>
>
Maybe the two assumption systems should be merged before the release of
version 1.0. It would be a bit weird to release version 1.0, and later
deprecate the old
Hi,
Can we delay 1.0 with some other version like 0.8 or so?
It would be nice if have atleast the solve mess being fixed in 1.0
Also we have yet not settled with a single assumption system.
AMiT Kumar
On Monday, August 31, 2015 at 11:25:31 PM UTC+5:30, Aaron Meurer wrote:
>
> It has come to my a
21 matches
Mail list logo
