On Tue, 12 Nov 2019 at 23:46, Jason Moore wrote:
>
> There are two things that I think are important:
>
> - don't include backwards incompatible changes in releases without a
> deprecation cycle (cycle should be measured in real time, not # cycles)
It isn't always possible to have a deprecation
To me the backwards compatibility thing is part of the problem. A lot
of the time the release blockers are about cleaning up some API that
is new since the previous release. We need to do it so that we aren't
forced to break it again in a later release. Or sometimes they are
about fixing a major
There are two things that I think are important:
- don't include backwards incompatible changes in releases without a
deprecation cycle (cycle should be measured in real time, not # cycles)
- don't introduce new features that we aren't confident we want to support
as public API
If we have strict
I've been thinking about how we can release SymPy more often. It's
apparent that there are two main things that have prevented it from
happening:
- My limited time to do the release
- The release blocking issues (the issues on the milestone on GitHub)
The first issue I hope should be solved by
Hi Ashlesha,
Please have a look at this for contributing to SymPy:
https://github.com/sympy/sympy/wiki/Introduction-to-contributing
-
Amit
On Monday, November 11, 2019 at 9:43:48 AM UTC, Ashlesha Kumar wrote:
>
> Hi,
>
> I am Ashlesha Kumar, undergraduate engineering student pursuing Computer
