On Sun, Nov 17, 2019 at 4:07 AM Oscar Benjamin
wrote:
>
> On Sun, 17 Nov 2019 at 05:01, Aaron Meurer wrote:
> >
> > Thinking more about the automation, I think we need to have the
> > release be 100% automated. Right now it is 90% automated (not counting
> > the problem of fixing blocker
On Sun, 17 Nov 2019 at 05:01, Aaron Meurer wrote:
>
> Thinking more about the automation, I think we need to have the
> release be 100% automated. Right now it is 90% automated (not counting
> the problem of fixing blocker issues).
>
> Oscar, it will be a good idea to make a note of anything in
Thinking more about the automation, I think we need to have the
release be 100% automated. Right now it is 90% automated (not counting
the problem of fixing blocker issues).
Oscar, it will be a good idea to make a note of anything in the
release process that isn't automated that should be. One
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
01 530-601-9791
>
>
> On Tue, Nov 12, 2019 at 3:28 PM Aaron Meurer wrote:
>>
>> 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
policy about those two and releasing is automated enough
that it isn't a time burden, could't we theoretically release after ever PR?
Jason
moorepants.info
+01 530-601-9791
On Tue, Nov 12, 2019 at 3:28 PM Aaron Meurer wrote:
> I've been thinking about how we can release SymPy more often. I
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
