Trex-devel May 2006

trex-devel@informatik.uni-goettingen.de

4 participants
12 discussions

Updatesite bug
by Dominic Evans 30 May '06

30 May '06

Hi, Just a minor bug, probably in the update site .xml file, but currently when you do an update it shows ${updateSiteDescription} (see screenshot) instead of some actual text. Regards, Dominic

2 2

0.5.2 ready to be released
by Helmut Neukirchen 30 May '06

30 May '06

The 0.5.2 JIRA roadmap is completely green and JUnit test are OK. Congratulations! Are there any objections to release it? (We already tagged it, but you may still object.) 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

2 1

0.5.2 release
by Helmut Neukirchen 30 May '06

30 May '06

Dear TRex developers, since I have to leave for the SAM conference this afternoon, we intend to release TRex 0.5.2 this noon. Hence, we should try to fix the remaining bugs ASAP. Currently, we have the following bugs open: TTC-76 UNRESOLVED Fix description of release process TTC-99 UNRESOLVED Add online help TTC-88 UNRESOLVED Merge Template doesn't merge charstring fields TTC-76 is part of the release process. TTC-99 will be fixed by either Martin or if he does not manage it this morning by me or Benjamin. correctly TTC-88 is more or less closed or do you, Dominic, have any further comments? (The solution proposed by Benjamin in a previous mail (invoke the pretty printer on a subtree just like it is done in inline template refactoring) should be deferred to 0.6.0.) I will try to review the RESOLVED, but not CLOSED issues and close them. Since the following issue was resolved by me, some other may test and close it: TTC-80 FIXED Modify JIRA 'Release Notes' template Furthermore, I will add a few sample test suites to be included on the TRex CD. Best regards, Helmut -- Helmut Neukirchen mailto:neukirchen@informatik.uni-goettingen.de Institute for Informatics http://www.swe.informatik.uni-goettingen.de University Goettingen, Lotzestr. 16-18 phone: +49 551 39 14695 D-37083 Goettingen, Germany fax: +49 551 39 14415

1 0

TRex help plugin
by Martin Bisanz 29 May '06

29 May '06

Dear all, a help plugin (de.ugoe.cs.swe.trex.ui.help) has been added to TRex. Currently, there are only two help pages, "Getting started" and "FAQs" (both manually copied from the wiki - I'm investigating tools for this). The Eclipse help system requires a few additional plugins in the target platform: - org.apache.lucene - org.eclipse.help.appserver - org.eclipse.help.base - org.eclipse.help.ui - org.eclipse.help.webapp - org.eclipse.tomcat - org.eclipse.ui.forms To enable the help plugin, please check your run configuration for these plugins (-> add required plugins) or start TRex via "Launch product". Thanks, Martin Bisanz

2 1

0.5.2 endgame, JIRA usage
by Helmut Neukirchen 24 May '06

24 May '06

Dear all, I think we may start some sort of "endgame" for the 0.5.2 TRex release. All TRex related issues are fixed, now. (Some off them still need to be closed). I think we should manually test the current build by just using TRex and report and fix any regressions. My current plan is to release TRex on Monday (which allows us to burn CDs for T3UC and SAM). Concerning JIRA, I experienced that it is probably good to have two different persons mark an issue as fixed and as closed. (It gives the bug fixer some feedback and involves some review by the issue closer.) I already changed the Wiki documentention on JIRA for developers. Furthermore, I came to the conclusion that we should use the issue type "Task" only for issues which should not appear in the release notes (i.e. the release note template will be modified to suppress tasks). Hence is "tasks" for Web site improvements, refactorings which would confuse the end user. (On the other hand there may be refactorings, e.g. performance tunings, which may be of interest for the end user; this would then be an issue type of "improvement".) Finally, I like to welcome Marting Bisanz as developer. He is working as a Master student on TRex and already contributed bug fixes. As part of his research, he will investigate pattern-based smell detection. Any feedback is welcome, Helmut -- Helmut Neukirchen mailto:neukirchen@informatik.uni-goettingen.de Institute for Informatics http://www.swe.informatik.uni-goettingen.de University Goettingen, Lotzestr. 16-18 phone: +49 551 39 14695 D-37083 Goettingen, Germany fax: +49 551 39 14415

2 1

TRex Outline View Slow
by Dominic Evans 23 May '06

23 May '06

Hi, TRex can be slow to initialise on a large (individual) TTCN-3 file that contains many elements (~10000 templates) as the outline view is slow to be created. It may only be possible to fix this with a design change. Currently the outline view is merely given the root node by the analyzer and it builds the tree for the outline by parsing through this looking for suitable elements. As we already go through the tree in TTCN3Analyzer, it may be better to build the list of basic elements to display there and give these directly to the outline to display (it can still work out nested elements itself). However, it may simply be that the SWT tree is slow to display large numbers of elements. Thoughts / comments? Regards, Dominic

2 2

JIRA 'Release Notes'
by Dominic Evans 19 May '06

19 May '06

Hi, Just a minor comment on JIRA-generated release notes. http://www.trex.informatik.uni-goettingen.de/jira/secure/ReleaseNote.jspa?p… If, as a user, I received this along with a new version of the tool, I would be unsure whether this first list was bugs that were fixed in this release or bugs that still remained in this release. Bugs Fixed, Improvements and New Features would be better choices. I don't know if it is possible to change this in JIRA configs, but if not I would recommend manually changing them before using this information in a new release announcement. Regards, Dominic

2 8

Nightly build working again, Developer's Corner documentation added
by Helmut Neukirchen 18 May '06

18 May '06

Dear TRex developers, Benjamin managed to make the trex.product and feature.xml platform independent, i.e. the installation of the nightly builds from the nightly build update site works again (it was broken for a few days, but the release update site was not affected.) (Solution: see "How to create a trex.product file which is platform independent?" on http://www.trex.informatik.uni-goettingen.de/trac/wiki/Developers#HOWTOs ) Furthermore, I have added some documentation at the Developer's Corner Wiki page. Most important for us are: http://www.trex.informatik.uni-goettingen.de/trac/wiki/JiraForDevelopers Summary: do not forget to close bugs and support using JIRA also for release management. http://www.trex.informatik.uni-goettingen.de/trac/wiki/CodingRules Summary: use SUN's Java coding rules and Eclipse default settings for formatting. Feedback is welcome (but please no lengthy discussion about coding rules: It's probably impossible to find a consensus. It's more important to actually have coding rules, not how they look like.) Bye, 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

TRex Bug Reporting
by Dominic Evans 16 May '06

16 May '06

Hi, I believe it is not evident from the current webpage where or how users should submit bug reports for TRex. Do you intend them to just mail problems to the trex-users mailing list or will they be expected to add them to the JIRA page themselves? We should make this clear somewhere. Incidentally it would now make sense to apply for the open source license for JIRA (rather than evaluation) now that the TRex webpage and source code are available. This is assuming you are happy with it (rather than bugzilla). Best regards, Dominic

2 3

[Fwd: Re: [Trex-devel] Website TOC Order]
by Benjamin Zeiss 12 May '06

12 May '06

we noticed this morning that the reply didn't go to the list. so here the answer for the sake of completeness. -------- Original Message -------- Subject: Re: [Trex-devel] Website TOC Order Date: Thu, 11 May 2006 18:43:10 +0200 From: Benjamin Zeiss <zeiss(a)cs.uni-goettingen.de> To: Dominic Evans <vnsd001(a)motorola.com> References: <20060511145705.GA3808(a)motorola.com> Hi Dominic, Dominic Evans wrote: > * Home > * TRex > o Documentation (ChangeLog could be linked within this node) > o Download (License could be linked within this node) > o Features > o Screencasts > o Screenshots > * Team (need better word for this) > o Contact (Mailing Lists could be linked within this node) > o Contributors > o Publications > * Links > > Any comments/thoughts? we just changed the structure a little. we think that changelogs are mostly viewed in conjunction with new releases or downloads. hence, the changelog is now located next to release announcements in the news and on the download page. then we think that publications is basically documentation and therefore combined the two pages. contact and contributors are also merged as "team". i hope you agree to these changes. we are not sure about the screenshots and screencasts. they could probably be merged too, but the nesting would be deeper in this case as the screenshots page is already pretty big. do you have any ideas concerning this? -- Benjamin Zeiss -- Benjamin Zeiss

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Trex-devel May 2006