Hello,
As I expected this 2.3.5 to be released (this was 3 weeks ago), I didn’t yet
add my latest merged pull requests to the patched 2.3.4 version we are
currently using in our build farm, but this seems to have stalled.
Dirk, what are your plans, should I wait or rather keep patching our
On 21.05.2015 05:20, Bill Deegan wrote:
William,
Of course your vote counts!
It's open source.
+1 :)
Dirk
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev
Hi Bill,
On 20.05.2015 16:36, Bill Deegan wrote:
All,
It's been a while since the last release and a number of fixes are in the repo,
is it a good time for a release?
I forget where we are with slots? Is that still on a branch or in default now?
the slots branch hasn't been merged yet.
Dirk,
Are you suggesting we should merge slots into default and push 2.4?
Or push what we have as 2.4 and then merge slots?
I'm thinking since slots will (could) break compatibility for some that we
should have a major version change? (3.0?)
If I remember correctly, that was our criteria for
On 20.05.2015 20:35, Bill Deegan wrote:
Could we push default as is as 2.3.5, and then merge slots and push that in a
couple weeks?
Then we could branch default as 2.3 prior to merge of slots?
Sure, I have no objections to that. After 2.3.5 we could also branch out from default to a 2.4
On 20.05.2015 21:20, Bill Deegan wrote:
Dirk,
Sounds great!
Is that something you execute?
:)
Well, I'd be willing to try. ;) However, this definitely requires to have the Wiki available again, so I can lookup the single steps
for the release procedure...and I'm not sure that I have all the
Dirk,
Sounds great!
Is that something you execute?
:)
-Bill
On Wed, May 20, 2015 at 12:14 PM, Dirk Bächle tshor...@gmx.de wrote:
On 20.05.2015 20:35, Bill Deegan wrote:
Could we push default as is as 2.3.5, and then merge slots and push that
in a couple weeks?
Then we could branch default
Bill,
On 20.05.2015 19:37, Bill Deegan wrote:
Dirk,
Are you suggesting we should merge slots into default and push 2.4?
Or push what we have as 2.4 and then merge slots?
if I got Jason right we don't have to wait for Parts to synchronize our development, so we're free to latch on. I suggest
On Wed, May 20, 2015 at 3:14 PM, Dirk Bächle tshor...@gmx.de wrote:
On 20.05.2015 20:35, Bill Deegan wrote:
Could we push default as is as 2.3.5, and then merge slots and push that
in a couple weeks?
Then we could branch default as 2.3 prior to merge of slots?
Sure, I have no objections
William,
Of course your vote counts!
It's open source.
-Bill
p.s. Plus you have a good first name so I give it a little more weight :)
On Wed, May 20, 2015 at 4:45 PM, William Blevins wblevins...@gmail.com
wrote:
On Wed, May 20, 2015 at 3:14 PM, Dirk Bächle tshor...@gmx.de wrote:
On
All,
It's been a while since the last release and a number of fixes are in the
repo, is it a good time for a release?
I forget where we are with slots? Is that still on a branch or in default
now?
-Bill
___
Scons-dev mailing list
Scons-dev@scons.org
11 matches
Mail list logo
