Re: 5.7.1 coming soon: b166778be merges devel into master.

2018-04-07 Thread Edward K. Ream
On Sat, Apr 7, 2018 at 8:11 AM, Viktor Ransmayr wrote: > Hello Edward, > > 2018-04-07 14:24 GMT+02:00 Edward K. Ream : > >> On Thursday, April 5, 2018 at 1:52:11 PM UTC-5, Viktor Ransmayr wrote: >>> >>> >>> Why not just use git pull from inside any VE you like? >>> >>> Because then I have to

Re: 5.7.1 coming soon: b166778be merges devel into master.

2018-04-07 Thread Viktor Ransmayr
Hello Edward, 2018-04-07 14:24 GMT+02:00 Edward K. Ream : > On Thursday, April 5, 2018 at 1:52:11 PM UTC-5, Viktor Ransmayr wrote: >> >> >> Why not just use git pull from inside any VE you like? >>> >> >> Because then I have to take care of installing all the required >> dependencies into the ded

Re: 5.7.1 coming soon: b166778be merges devel into master.

2018-04-07 Thread Edward K. Ream
On Thursday, April 5, 2018 at 1:52:11 PM UTC-5, Viktor Ransmayr wrote: > > > Why not just use git pull from inside any VE you like? >> > > Because then I have to take care of installing all the required > dependencies into the dedicated VE myself ! > Imo, you are making more work for yourself,

Re: 5.7.1 coming soon: b166778be merges devel into master.

2018-04-05 Thread Viktor Ransmayr
Hello Edward, On Thu, Apr 5, 2018, 16:09 Edward K. Ream wrote: > On Thursday, April 5, 2018 at 12:51:20 AM UTC-5, Viktor Ransmayr wrote: >> >> >> If #847 would be resolved, then I could set up a dedicated virtual >> environment (VE) for the devel- and/or master-branch - and - would be able >> to

Re: 5.7.1 coming soon: b166778be merges devel into master.

2018-04-05 Thread Edward K. Ream
On Thursday, April 5, 2018 at 12:51:20 AM UTC-5, Viktor Ransmayr wrote: > > > If #847 would be resolved, then I could set up a dedicated virtual > environment (VE) for the devel- and/or master-branch - and - would be able > to provide **user** feedback early ... > Why not just use git pull from

Re: 5.7.1 coming soon: b166778be merges devel into master.

2018-04-04 Thread Viktor Ransmayr
2018-04-05 0:21 GMT+02:00 Edward K. Ream : > On Wed, Apr 4, 2018 at 1:15 PM, Viktor Ransmayr > wrote: > > However, if possible at all, I'd like issue #847 to be resolved before Leo >> 5.7.1 will be released! >> > ​ > This is up to Matt, but imo one advantage of github-only releases is that > we d

Re: 5.7.1 coming soon: b166778be merges devel into master.

2018-04-04 Thread Edward K. Ream
On Wed, Apr 4, 2018 at 1:15 PM, Viktor Ransmayr wrote: However, if possible at all, I'd like issue #847 to be resolved before Leo > 5.7.1 will be released! > ​ This is up to Matt, but imo one advantage of github-only releases is that we don't have to solve these problems for every minor (5.7.x) r

Re: 5.7.1 coming soon: b166778be merges devel into master.

2018-04-04 Thread Viktor Ransmayr
Hello Edward, hello Matt, 2018-04-04 15:15 GMT+02:00 Edward K. Ream : > On Wednesday, April 4, 2018 at 8:13:25 AM UTC-5, Edward K. Ream wrote: > > This is the first step towards releasing 5.7.1. >> > > Note to Matt. There should be no need to create a pip-installable > version. This release will

Re: 5.7.1 coming soon: b166778be merges devel into master.

2018-04-04 Thread Edward K. Ream
On Wednesday, April 4, 2018 at 8:13:25 AM UTC-5, Edward K. Ream wrote: This is the first step towards releasing 5.7.1. > Note to Matt. There should be no need to create a pip-installable version. This release will only appear on GitHub, not SourceForge. Edward -- You received this message be