Thanks a lot Görel, this sounds excellent.
Eric
On 7 March 2012 13:44, Görel Hedin <gorel_at_cs.lth.se> wrote:
> Hi Eric,
>
> Thanks for your input. I understand your frustration!
>
> We are currently working with getting a better test framework in place. It takes a bit time though, because we all have so many other things to do!
>
> One thing we plan to do is to introduce a stable branch with less frequent updates and that includes the necessary documentation. Once that is in place, you might consider switching to that branch for JastAddJ.
>
> We are also planning to add testing of 3rd party tools to our nightly tests. This way, we could test your code on our experimental versions before releasing to stable.
>
> Meanwhile, you of course need better information about our changes. And perhaps we could be more restrictive with certain changes until the stable branch is in place. We'll discuss some measures and get back to you later this week. Thanks for the info about your mailing list - that should certainly help.
>
> Cheers,
> Görel
>
> 7 mar 2012 kl. 12.28 skrev Eric Bodden:
>
>> Hi all.
>>
>> As some of you probably know by now, we are having a nightly build
>> process for the abc compiler and some of its related projects,
>> including JastAdd. During the past few weeks it has happened
>> repeatedly that there were non-compatible code changes in JastAdd,
>> such as renaming of AST nodes etc. The way this currently works
>> (without announcement, without a change log and without instructions
>> on how to adapt to the new structure), this can be pretty annoying for
>> projects like ours, as we need to spend a lot of time to figure out
>> how to update our client code to make it work again.
>>
>> Of course I know that changes are necessary to keep the system up to
>> date, but I would appreciate if we could find some solution that would
>> allow "clients" like us to update their code base quickly according to
>> those changes. This could be as simple as writing appropriate
>> instructions in the commit logs or something more elaborate. In
>> addition, there is a mailing list that JastAdd maintainers could
>> subscribe to: http://mailman.cs.mcgill.ca/mailman/listinfo/abc-testlogs
>> This list receives nightly result emails from our integrated build. An
>> example email from last night is attached.
>>
>> I wonder what would be your take on this.
>>
>> Best wishes,
>> Eric
>> --
>> Eric Bodden, Ph.D., http://bodden.de/
>> Head of Secure Software Engineering Group at EC SPRIDE
>> Principal Investigator in Secure Services at CASED
>> Tel: +49 6151 16-75422 Fax: +49 6151 16-72051
>> Room 3.2.14, Mornewegstr. 30, 64293 Darmstadt
>> <example-mail.txt>_______________________________________________
>> JastAdd mailing list
>> JastAdd_at_cs.lth.se
>> https://mail1.cs.lth.se/cgi-bin/mailman/listinfo/jastadd
>
> _______________________________________________
> JastAdd mailing list
> JastAdd_at_cs.lth.se
> https://mail1.cs.lth.se/cgi-bin/mailman/listinfo/jastadd
--
Eric Bodden, Ph.D., http://bodden.de/
Head of Secure Software Engineering Group at EC SPRIDE
Principal Investigator in Secure Services at CASED
Tel: +49 6151 16-75422 Fax: +49 6151 16-72051
Room 3.2.14, Mornewegstr. 30, 64293 Darmstadt
Received on Wed Mar 07 2012 - 14:08:14 CET