We are happy to announce AgileReview v0.9.1. A lot of bug fixes but also some new features made their way into our latest release!
The release improves the Cleanup-Action. It is now possible to clean up more than one project as well restrict the Cleanup-Action to comments in state ‘closed’.
Thanks to everybody who provided feedback!
AgileReview v0.9.1 is available via our update site as usual:
We are happy to announce AgileReview v0.9.0. We decided to skip 0.8.5 and move to 0.9.0 in order to clarify our point of view that the current AgileReview Plugin is now in a stable state. Therefore, we also decided to drop the Beta-Status.
The release provides file paths of commented files and comment replies as part of an extended XLS-export format. We also updated the export templates to provide you with examples on how to use our export data. The template can be downloaded in XLS format and XLSX format.
AgileReview v0.9.0 is available via our update site as usual:
In addition to our previously announced move to GitHub we decided to split the development for AgileReview v1.0.0 and the current stable version of AgileReview into separate projects.
The project is now spilt up into
Within this overall move to GitHub we also finally decided to use the GitHub issue-tracker, which can be found on our Bugs & Requests page.
Already in January we moved our main development repository to GitHub. This move was affected by our decision to move from SVN to Git. This will help us to focus more easily on our main goal for the next months. Please note, that we keep the SVN repository on SourceForge but will not do any further commits there. All code can now be found at the following locations:
- AgileReview-Plugin (current stable):
git clone email@example.com:AgileReview-Project/AgileReview-Legacy-Plugin.git
Use branch “master” for releases or branch “next_Release” for the current development iteration.
- AgileReview-Plugin (v1.0.0):
git clone firstname.lastname@example.org:AgileReview-Project/AgileReview-EclipsePlugin.git
Use branch “master” for the future version v1.0.0. depends on the CoreLib project.
- CoreLib (required for AgileReview v1.0.0):
git clone email@example.com:AgileReview-Project/AgileReview-CoreLib.git
- Findbugs Importer (Prototyp/Demo, compatible with v1.0.0):
git clone firstname.lastname@example.org:AgileReview-Project/AgileReview-Findbugs.git
SourceForge (updated erratically, Eclipse plugin only):
git clone git://git.code.sf.net/p/agilereview/git agilereview-git
As Sourceforge has announced to close its HostedApps program, we have to move our Mantis-Bugtracker to a new location: http://bugs.agilereview.org
All tickets and users have been migrated except the user passwords, which have been made not available by Sourceforge. Thus if you had an account previously in Mantis, just go to the lost-my-password-page and type in your sourceforge user name and sourceforge email address. Than qou will get an email allowing you to set your new password (decoupled now from your Sourceforge account).
Happy Bugtracking 🙂
After a longer break, we are happy to announce further development steps for the new version of AgileReview.
The targeted version 1.0 comes up with a new modularized architecture and core libraries which are independent from the eclipse world. This enables you to integrate AgileReview as a marker tool for your static analysis tool or any other batch runner, which should create new AgileReview comments within eclipse or without eclipse.
We will provide a short overview about the current development steps and the current state in a short demo on the Eclipse DemoCamp 2014 in Munich (http://wiki.eclipse.org/Eclipse_DemoCamps_Luna_2014/Munich).
We recently noticed, that AgileReview is featured in the latest issue of the German journal “Eclipse Magazin” which is available since 9/27/2013.
Author Simon Olofsson provides you with a comparison of AgileReview and Review For Eclipse (R4E), an Eclipse top-level project in incubator status. R4E is also known to the AgileReview team. We discussed the different approaches of both tools already at the Eclipse DemoCamp Kaiserslautern in 2011, where we met Steffen Pingel, one of the developers of R4E.
The criticism provided by Simon is really appreciated. We know that AgileReview still has rough edges. While the positive feedback fortifies us, the constructive criticism helps us to further improve AgileReview.
The mentioned issue of the magazine is available at German newsdealers or online at https://jaxenter.de/magazines/Eclipse-Magazin-613-167429.
P.S.: Altough you did not hear much from us we did not stop the development of AgileReview. We are still working on the completely reworked AgileReview 1.0!
Some things went terribly wrong in the last days. We’re really sorry for that!
First of all, when moving from SourceForge web-space to our own server, we did not manage to properly configure the update sites for the agilereview.org domain. We tried to fix this issue in the last days but some misconfigurations kept the update sites from working. This has been fixed (and tested!) so that the update sites are up and running again.
Second, the bug fix for bug 0000141 caused some software regression that rendered AgileReview unusable. The fix was reverted and AgileReview can be used as usual again. A fix for bug 0000141 will be released with v0.8.5. Both, stable and nightly builds can be retrieved via our update sites or from the SourceForge “Files” section. The jar-file for v0.8.4 was missing in the last days but is available again.
Today, we published the bug fix release v0.8.4, which was mainly driven by issues reported by the community. Thanks for the feedback!
This release solves the following problems:
- 0000136: [CommentSummaryView] NullPointerException if selection filter of ReviewExplorer is toggled and ICommandService is not available
0000141: [ReviewExplorer] Reviews not update when switching branches with git
- 0000143: [XMLStorage] Using egit and switching between branches may cause lose of active AgileReview Source Folder
- 0000142: [Other] Multiple open review projects
- 0000135: [Annotations] ClassCastException when editing annotation tags manually
Also, the update sites are available via their old URL again:
Don’t worry, the update sites are also available via their SourceForge URL.
Beside the current development of the first 1.0 release of AgileReview, the last days we worked on moving our webspace from SourceForge to a new server. So unfortunately it happened, that the UpdateSite of AgileReview stopped working.
Now hopefully all webspace related issues are fixed and you will be able to install AgileReview via our UpdateSite again. If there are any issues left do not hesitate to contact us!
Today we released the bug fix release v0.8.3, which was mainly driven by issues reported of the community, thanks for all feedback! This release mainly solves the following problems:
- Adding comments in Zend Studio does not work.
- The On-Save action “formatting code” destroys code and comment tags when adding or deleting comments.
- Commenting JavaDoc and have formatting code on save enabled, will result in additional lines which are not removed after comment deletion
- Project-Cleanup does not remove all tags consistent to manual removing via AgileReview-Perspective
For more information see the changelog.
In late September the Eclipse Day Delft 2012 will take place in Delft, NL and we are very interested in this event. It “will focus on tools and techniques to support the software development process”. Furthermore, “Quality Assurance” is one of the main topics. Therefore, the Eclipse Day Delft would be the ideal possibility to present AgileReview to a rather broad audience.
However, (from a students point of view) it is a long and expensive way from Kaiserslautern to Delft by any transportation possibility. As we cannot afford the trip, we haven’t submitted a proposal for a presentation yet. We decided to first of all look for persons or companies that are willing to (partially) take over the costs for this trip.
Whether you are a user of AgileReview and are looking for a way to give some rewards to the developers of your favourite review tool or you simply want to see us presenting AgileReview in Delft: this would be the perfect opportunity to do so!
If you are willing to support us, contact us via team email address developers -at- agilereview.org.
Our Agilereview webpage got another section called Publications. There you can find all the publications of the Agilereview development team. The publications currently include presentations and magazine articles.
Due to some user feedback and bugs that were detected recently we decided to do an additional release while continuing development of AgileReview v1.0.
The new version includes an option to perform the cleanup process for single reviews (issue 120). Other changes are:
- 0000127: Review data will not be stored when using the 'create new review' wizard
- 0000121: 'Delete Resource' in DetailView deletes comment but not tags
- 0000122: disable unavailable options for closed reviews in ReviewExplorer context menu
We want to thank all users that provided us with feedback and are looking forward to getting more from you. This feedback helps us to continuously improve the quality of AgileReview.
First of all, we want to thank the Software Technologie Initiative Kaiserslautern e.V., which gave us the possibility to present AgileReview at their JourFix.
The Jour Fixe itself was a big success. Almost 30 participants, from different regional companies and institutes attended our 40-minute-talk. Following, there were some very interesting questions about the project as well as some useful suggestions on features for future releases (e.g. the integration of checklists). Also during the Meet&Great-session we got really nice and positive feedback.
Some impressions of the presentation can be found in this long and interesting blog post about AgileReview of Maud Schlich.
Thanks to all for the kind feedback!
During last week’s Eclipse regular’s table in Kaiserslautern we were asked to give a presentation at the Software Technology Initiative Kaiserslautern jour fixe. The presentation will be held at
on April, 18th, 17:30-19:30.
We will cover basic information on AgileReview, some in-depth architecture descriptions and an insight into the current architecture rework. Join us if you are interested in AgileReview and want to get first-hand knowledge from the developers.
Special thanks goes to Claudia Könnecke, verit Informationssysteme GmbH, who coordinated the regular’s table and kindly asked whether we were interested in the STI presentation!
It’s been a while since our last release, but finally we managed to roll out AgileReview v0.8.1.
Besides some minor bug fixes, the handling of Review Source Folders was improved. As suggested by some users an option to suppress warnings due to a missing Review Source Folder was added. Furthermore, the preferences UI was updated.
We are looking forward to getting feedback from you, so that we can continuously improve the quality of AgileReview. Visit our change log to get to know everything about the new features and bug fixes.
A couple of days has been gone since we introduced AgileReview to the JUG Ostfalen community. At this point we have to thank a view people for this great opportunity. For everyone who missed our presentation, you can find a short review on the community site.
First, we want to thank Uwe Sauerbrei for the invitation to this presentation. But we also want to thank the booster club for computer science of the University of Kaiserslautern (FIT), who took over the costs for the long (and from a students point of view expensive) trip to Braunschweig and therefore rendered our presentation possible.
Since we have been receiving some emails with questions the last days, we updated the FAQ page (and arranged it in a neat way) , so it hopefully will answer your questions.
Still, if you have questions which are not answered by the FAQ, feel free to ask us by sending an email to email@example.com.
Additionally, in order to honor our users and supportes, the new users & supporters page shows all users (at least those we know of) and supporters of AgileReview. If you actively use AgileReview in your process and want to be named on this page, feel free to contact us.
We are proud to announce that we are invited to join the Jug-Ostfalen group at the 20th of January as presenters. We will introduce the functionalities of AgileReview and will talk about its implementation and future plans. Perhaps you are interested to get a personal introduction into AgileReview and its backgrounds? Then register on Jug-Ostfalen to join us.
We are looking foward to seeing you!
Due to the release of AgileReview v0.8.0 the Quickstart document was updated. Major changes include the new multi-color support of comments. Download the Quickstart document here.
It is done! The next version of AgileReview is online!
Besides the new color management this release brings some very important bug fixes. So we recommend to update to version 0.8. We are looking forward to getting feedback from you, so that we can continously improve the quality of AgileReview. Visit our change log to get to know everything about the new features and bug fixes.
We are proud to announce that AgileReview is presented as cover story of eclipse Magazin Germany (issue 1.12). The article covers basic information as well as in-depth architectural details about AgileReview.
Some of our users experienced SVN related problems due to occurences of both Windows and Unix line endings. Although this issue was fixed in v0.7.1 the problem might persist in “old” review data. Therefore, we developed a small toolkit which enables you to convert the line endings of all files of a AgileReview source folder to your systems line endings (download). Furthermore, you can check the validity of these files. You will be notified about problems like empty files or erroneous XML structures which currently can cause failures of AgileReview. These issues will be regarded in the next bug-fix release which is currently under development.
Some of you provide us with bug reports for version 0.7.0. We managed to fix all these issues and released them in v0.7.1. For more information on the changes see our changelog page.
Thanks to all of you who provided us with feedback!
We are proud to announce that we will attend the eclipse DemoCamp on November 24th in Kaiserslautern in order to present AgileReview to the eclipse community. If anybody is interested in more information about AgileReview or talking to us personally, feel free to inform you about the DemoCamp here and join us!
We are proud to announce the next Release (v0.7) of AgileReview. We apologize for the delay, but now we managed to fully integrate our plug-in into the eclipse internal refactoring mechanisms. Continue reading
As mentioned in the last post, the release of v0.7.0 of AgileReview had to be delayed due to broken refactoring stability. We managed to fix these issues and are now testing whether the refactoring actions “move” and “rename” work well. Continue reading
It was planned to release v0.7.0 with lots of new features on the 31th of August. Unfortunately, some changes broke the refactoring stability of AgileReview. Continue reading
Some days ago, the implementation phase of AgileReview v0.7 ended up. The main features that were implemented are the “configurable source folder” and “extended language support”. Continue reading
The next version of Eclipse is online. It is called Indigo.
We checked compatibility of the AgileReview plugin with this version. Everything works fine. So please keep using our plugin also on the newest version of Eclipse.
during development we decided to establish a more intuitive domain for AgileReview and now here is it!
This site is now also available via agilereview.org!
Furthermore, all developers can also be contacted using <first name>.<surname>@agilereview.org now.
Have fun and keep updated. The next release is comming soon.
Today we decided about the features and changes to provide in the next release. Our planning and the current status for this iteration can be viewed in the features->planning section.
If you have some other nice ideas contact us and we will decide whether we are able to integrate your proposal in one of the next releases.
Today the feature-planning page has been added. This is because we want to show you which steps we already did and which we want to do in the next iteration(s). See here. We also look forward to get some ideas and wishes from you. So do not hesitate to contact us.
Planning of new interations/Implementation of new features will not start until beginning of April. This is due to the current beta testing phase and our current work on the documentation.
A ChangeLog was added in order to trace all updates. (see here)
An update has been released that fixes a null-pointer exception that occured when switching between editors after switching from the AgileReview perspective to any other perspective. We recommend to update the AgileReview plugin via update site. (see ChangeLog)
Just some minutes ago the first public beta (v0.6.0) was released. It can be downloaded using the update site or via file download.
As a reaction to some suggestions by our alpha testers, we added a “Quick Start” page to provide a short introduction to the AgileReview plugin.
@all testers: Thanks for testing and supporting our project 🙂