Trex-devel June 2006

trex-devel@informatik.uni-goettingen.de

4 participants
6 discussions

0.5.3 release planning
by Helmut Neukirchen 06 Jul '06

06 Jul '06

Dear all, currently, we have the following issues for 0.5.3 open: TTC-137 Add more complex tests for inline template parameter TTC-142 Allow merge refactoring to leave originals as delegates TTC-138 Add tests for all refactoring using templates involving record of/set of/type record length TTC-98 Create tests for ASTUtil utility functions. TTC-46 Refactoring: Undo across all effected files? TTC-96 Add tests for Merge Template refactoring I like to take some load from Dominic and thus have question concerning assignment of the following issues: TTC-142 is currently assigned to Dominic: Do you intend to work on it or shall I investigate it (and you possibly implement it lateron)? TTC-98 is currently assigned to Dominic: Do you intend to implement the tests? TTC-46 is currently assigned to Dominic: Do you intend to tackle it or shall we assign it to Martin? For the remaing ones (adding more JUnit tests), I feel responsible. (Even though I am currently a bit busy.) Furthermore, all developers are invited to close those bugs marked as fixed by other ones (or respectively re-open if necessary). Best regards, Helmut -- Helmut Neukirchen mailto:neukirchen@informatik.uni-goettingen.de Institute for Informatics http://www.swe.informatik.uni-goettingen.de University of Göttingen, Lotzestr. 16-18 phone: +49 551 39 14695 D-37083 Göttingen, Germany fax: +49 551 39 14415

3 7

TRex website - updatesites
by Dominic Evans 16 Jun '06

16 Jun '06

Hi all, A very minor point. Currently if you accidentally (or otherwise) navigate to the updatesite URLs you get the simple message "trex releases update site. no other content here..." Might I suggest that instead we auto-redirect people to either http://www.trex.informatik.uni-goettingen.de/trac/wiki/Download or http://www.trex.informatik.uni-goettingen.de/trac/wiki/TrexInstallation e.g. using the short index.php <? Header( "HTTP/1.1 301 Moved Permanently" ); Header( "Location: http://www.trex.informatik.uni-goettingen.de/trac/wiki/Download" ); ?> Seeing as Eclipse directly references the site.xml file it should not be effected by this change. Best regards, Dominic

2 1

TTC-46 undo across all effected files
by Dominic Evans 09 Jun '06

09 Jun '06

Hi all, Firstly a quick question, do you intend to bring the 30th June release date for 0.5.3 forward (seeing as the roadmap is nearing completion), or do you intend to schedule more things to be fixed before 0.5.3 and stick with 30th June? Whichever way, I wonder if TTC-46 could be re-targeted at 0.5.3 bugfix release? Although it is currently marked as an improvement, I would actually consider it as a bug - the user expects 'undo' to undo everything they performed in the last operation (as it does in JDT). http://www.trex.informatik.uni-goettingen.de/jira/browse/TTC-46 Regards, Dominic

2 1

testMergeInresTemplate
by Dominic Evans 08 Jun '06

08 Jun '06

Hi all, The JUnit test 'testMergeInresTemplate' currently fails with a refactoring exception because the ConnectionRequest template is not marked for parameterisation. Was this test constructed by hand to indicate a refactoring/suggestion that should exist? i.e. are you saying you would like the following to be merged?? template MDATind ConnectionRequest:={ mData:={ iPDUType:=CR, seqNo:=omit, iData:=omit } } template MDATind DataTransfer(UserPDU data, SequenceNumber no):={ mData:={ iPDUType:=DT, seqNo:=no, iData:=data } } Or is this just a test that was written against the previously buggy detection and should be re-targeted or removed? Best regards, Dominic

4 5

Merge template rules and undefined field types
by Dominic Evans 07 Jun '06

07 Jun '06

Hi all, A minor development question. In the merge template rules, before adding a marker, we check to see if the types have been defined for the fields of the template (as we need this information into to add formal parameters). Therefore, if one of the field types isn't defined then these potentially merge-able templates are ignored. We have 3 options a) continue exactly as we are already and just ignore them b) continue to ignore the potential merge, but add an error marker to indicate that the type hasn't been defined for that template field c) add a marker in the usual way to point out the potential merge and just fall-back to the error message that is displayed when the user tries to perform the refactoring (I have always had the same check for field type definitions in checkInitialConditions() in the merge processor). b) may be preferable but then it may give the false idea to the user that these highlighted types are the only ones that are not defined in the project (i.e. we would really need to be adding errors for all undefined types that are used. Thoughts? Regards, Dominic

2 1

0.5.3 bug fix release
by Helmut Neukirchen 06 Jun '06

06 Jun '06

Dear TRex developers, here in Göttingen, we came to the conclusion, that instead of adding further functionality, our short-term priority should be quality to prevent losing users (and potential contributors) due to quality problems. Hence, we have created a 0.5.3 TRex release in Jira, containing mainly bug fixes and further JUnit tests. Review whether you are happy with this schedule, assignments. Feel free to discuss, change and/or add issues. Best regards, Helmut -- Helmut Neukirchen mailto:neukirchen@informatik.uni-goettingen.de Institute for Informatics http://www.swe.informatik.uni-goettingen.de University of Göttingen, Lotzestr. 16-18 phone: +49 551 39 14695 D-37083 Göttingen, Germany fax: +49 551 39 14415

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Trex-devel June 2006