Hi all,
please do not forget, that Yade has already a rich opportunity
to create semi-unit-tests (yade --test) and nice semi-integration-tests
(yade --check). Sure, one can create unit tests for pure C++-functions
using boost::unit_test, cppunit or googletest etc., but I would propose
first to ext
Hello all,
last several years I did Yade releases and the process was
the following. Before the release was done I created the corresponding
release-branch (for example 0.60 [1]) and just tagged the new
Yade version there. It worked relatively good.
--> develop
Hello Janek,
thanks for the fix! I have checked it and it really resolves the problem
with the newer CGAL. I will reactivate CGAL-function for the
Debian-build again.
Regards
Anton
Am Mo., 7. Jan. 2019 um 13:44 Uhr schrieb Janek Kozicki :
>
> Bruno Chareyre said: (by the date of Sun, 6 Jan
Bruno Chareyre said: (by the date of Sun, 6 Jan 2019 17:08:12 +0100)
> Thanks for raising this major issue. It would be great to populate unit
> tests indeed.
>
> I recently
> https://github.com/yade/trunk/commit/b5fbefc6463294f580296cb5727dbbfd733fa8a0
> introduced a regression test for the
Bruno Chareyre said: (by the date of Mon, 7 Jan 2019 16:59:53 +0100)
> Daily builds would be based on the develop branch.
good, that answer my question from other mail.
> > (by the way, with a tighter control on development, would we still
> > need a distinction between "yade" and "yadedai
Bruno Chareyre said: (by the date of Mon, 07 Jan 2019 15:23:11 -)
> To be honest that wiki hosted on some 3SR server will get less and less
> support with Rémi gone.
> I don't even know which computer exactly is hosting this.
>
> Finding a replacement would be a good thing. Gitlab is hos
Bruno Chareyre said: (by the date of Sun, 6 Jan 2019 23:04:13 +0100)
> Hi Janek, I think we are on the same line more or less. We only differ on
> practical details, mainly the notion of merge request in gitlab.
yes, I noticed the same thing too. It seems that my suggestion can be
applied in
On 1/7/19 1:12 PM, Jerome Duriez wrote:
I could see just one point having an additional "develop": in the case
where eg yadedaily packages would be built from master only, and not
from develop. Is this a plan ?
Daily builds would be based on the develop branch.
(by the way, with a tighter
To be honest that wiki hosted on some 3SR server will get less and less support
with Rémi gone.
I don't even know which computer exactly is hosting this.
Finding a replacement would be a good thing. Gitlab is hosting wiki pages
indeed (even Github actually) but I don't if it is possible to just
Bruno Chareyre said: (by the date of Sun, 6 Jan 2019 15:34:11 +0100)
> > Hi Janek,
> > I think that was the right fix, thanks.
> > Note that yade is not using the periodic triangulation implemented in CGAL
> > [1] so there is no question on that point afaik.
> > Bruno
good, great to know. Dur
Hi,
Trying to (somewhat, at least) follow the discussion, I'd come back to
The main branches
* master
* develop
Definitely.
in connection with the above-mentioned web post [1].
Thus, a question: What would be the purpose splitting / the definition
of "master" and "develop" ?
11 matches
Mail list logo
