On 2015-06-05 12:00, Rikki Cattermole wrote:
I wonder if we could integrate a bit more with travis
The problem with Travis CI is that it's limited to Linux and OS X 64bit.
D supports Windows and FreeBSD and 32bit versions as well.
BTW, DMD is already tested by Travis CI [1], but only for
Of many things that Rust got right, this is, in my opinion,
something they did wrong. Quick release cycles only make sense in
both bleeding edge model and with availability of excess
developer resources. No amount of planning and management can
compensate for things not being ready.
On 5/06/2015 6:00 p.m., Dicebot wrote:
Of many things that Rust got right, this is, in my opinion, something
they did wrong. Quick release cycles only make sense in both bleeding
edge model and with availability of excess developer resources. No
amount of planning and management can compensate
On 5/06/2015 6:10 p.m., Dicebot wrote:
On Friday, 5 June 2015 at 06:08:41 UTC, Rikki Cattermole wrote:
Of course we could always get the CI to auto build a full release
every day available for download.
It would then be just a matter of picking one set and promoting as a
version.
Perfect for
On Friday, 5 June 2015 at 06:42:06 UTC, Rikki Cattermole wrote:
And shouldn't the CI be doing regression testing already?
The autotester runs the unit tests that are in druntime, Phobos,
and dmd. It catches a lot of stuff and generally prevents us from
merging bad code. But it can't possibly
On Friday, 5 June 2015 at 06:42:06 UTC, Rikki Cattermole wrote:
And shouldn't the CI be doing regression testing already?
Changelog perhaps should be updated with a commit then?
In perfect world tests provide full coverage and language spec is
clearly defined. In practice each single beta
On Friday, 5 June 2015 at 06:08:41 UTC, Rikki Cattermole wrote:
Of course we could always get the CI to auto build a full
release every day available for download.
It would then be just a matter of picking one set and promoting
as a version.
Perfect for e.g. testing.
Picking random commit
On Friday, 5 June 2015 at 06:00:46 UTC, Dicebot wrote:
Of many things that Rust got right, this is, in my opinion,
something they did wrong. Quick release cycles only make sense
in both bleeding edge model and with availability of excess
developer resources. No amount of planning and
On 5/06/2015 8:28 p.m., Jonathan M Davis wrote:
On Friday, 5 June 2015 at 06:42:06 UTC, Rikki Cattermole wrote:
And shouldn't the CI be doing regression testing already?
The autotester runs the unit tests that are in druntime, Phobos, and
dmd. It catches a lot of stuff and generally prevents
On Friday, 5 June 2015 at 10:00:17 UTC, Rikki Cattermole wrote:
I wonder if we could integrate a bit more with travis and have
a big list of projects compiling + testing against HEAD.
Would be an excellent indicator.
Maybe even have this as part of dub repo?
I do it for small set of projects
On Friday, 5 June 2015 at 10:00:17 UTC, Rikki Cattermole wrote:
On 5/06/2015 8:28 p.m., Jonathan M Davis wrote:
On Friday, 5 June 2015 at 06:42:06 UTC, Rikki Cattermole wrote:
And shouldn't the CI be doing regression testing already?
The autotester runs the unit tests that are in druntime,
On Friday, 5 June 2015 at 11:09:27 UTC, Dicebot wrote:
By the way dub master has been broken with dmd master for ages
: https://jenkins.dicebot.lv
It usually is, which usually means that I'm forced to install a
release version of the compiler just to build dub, since I'm
almost always using
On Friday, 5 June 2015 at 12:20:06 UTC, Jonathan M Davis wrote:
On Friday, 5 June 2015 at 11:09:27 UTC, Dicebot wrote:
By the way dub master has been broken with dmd master for ages
: https://jenkins.dicebot.lv
It usually is, which usually means that I'm forced to install a
release version
On Friday, 5 June 2015 at 14:11:06 UTC, Steven Schveighoffer
wrote:
On 6/5/15 1:53 AM, Andrei Alexandrescu wrote:
Rust will do it:
http://opensource.com/business/15/6/rust-6-week-release-cycle
Would be so nice if we had the resources to do that. There
have been a
couple of initiatives in the
On 6/5/15 1:53 AM, Andrei Alexandrescu wrote:
Rust will do it:
http://opensource.com/business/15/6/rust-6-week-release-cycle
Would be so nice if we had the resources to do that. There have been a
couple of initiatives in the past, but the folks who wanted to do the
release just got busy with
On 2015-06-05 08:10, Dicebot wrote:
Picking random commit and calling it a version is not really
releasing. For me release implies strict regression testing and nice
changelog at the very least.
Very good point.
--
/Jacob Carlborg
On 6/5/15 2:03 PM, Dicebot wrote:
Martin was going for http://wiki.dlang.org/DIP75
OK, good, this needs an executive decision. We need a process to be
blessed first before we talk about release frequency. Then everything
backfills from there.
-Steve
On Friday, 5 June 2015 at 14:11:06 UTC, Steven Schveighoffer
wrote:
On 6/5/15 1:53 AM, Andrei Alexandrescu wrote:
Rust will do it:
http://opensource.com/business/15/6/rust-6-week-release-cycle
Would be so nice if we had the resources to do that. There
have been a
couple of initiatives in the
On Friday, 5 June 2015 at 12:21:20 UTC, Dicebot wrote:
On Friday, 5 June 2015 at 12:20:06 UTC, Jonathan M Davis wrote:
On Friday, 5 June 2015 at 11:09:27 UTC, Dicebot wrote:
By the way dub master has been broken with dmd master for
ages : https://jenkins.dicebot.lv
It usually is, which
On 6/5/15 3:19 PM, Steven Schveighoffer wrote:
On 6/5/15 2:03 PM, Dicebot wrote:
Martin was going for http://wiki.dlang.org/DIP75
OK, good, this needs an executive decision. We need a process to be
blessed first before we talk about release frequency. Then everything
backfills from there.
On Friday, 5 June 2015 at 19:19:33 UTC, Steven Schveighoffer
wrote:
On 6/5/15 2:03 PM, Dicebot wrote:
Martin was going for http://wiki.dlang.org/DIP75
OK, good, this needs an executive decision. We need a process
to be blessed first before we talk about release frequency.
Then everything
On 6/5/15 12:28 PM, David Soria Parra wrote:
On Friday, 5 June 2015 at 19:19:33 UTC, Steven Schveighoffer wrote:
On 6/5/15 2:03 PM, Dicebot wrote:
Martin was going for http://wiki.dlang.org/DIP75
OK, good, this needs an executive decision. We need a process to be
blessed first before we
On 6/5/15 4:31 PM, Andrei Alexandrescu wrote:
On 6/5/15 12:28 PM, David Soria Parra wrote:
On Friday, 5 June 2015 at 19:19:33 UTC, Steven Schveighoffer wrote:
OK, good, this needs an executive decision. We need a process to be
blessed first before we talk about release frequency. Then
23 matches
Mail list logo
