List view
Let's plan a post-Hacktoberfest release.
Due by November 29, 2020•0/1 issues closed- No due date•13/13 issues closed
- Due by May 4, 2019•1/1 issues closed
- Due by March 3, 2019•72/72 issues closed
Reference Explorer and whatever else we get done by then will make a great christmas / new year's present to the VBA / VB6 community :)
Due by January 14, 2019•27/27 issues closedFollow Up 2.3.0 with an early-scheduled maintenance release. The idea is to keep reducing technical debt, keep improving the Ducky's stability and squash some more bugs!
Due by December 30, 2018•24/24 issues closedThe 2.3.0 release in the 2.x release cycle. Goals include: - vb6 go-live - bugfree autocomplete - stability improvements
Due by November 25, 2018•47/47 issues closed2.2.0 Release Milestone
Due by April 8, 2018- Due by November 13, 2017
- Due by October 15, 2017•38/38 issues closed
Originally planned as the February 2017 release, 2.0.12 just got a little bit bigger, and now involves a complete overhaul of how inspections work internally. Pushed to early March.
Due by March 4, 2017•54/54 issues closedThis version of Rubberduck will feature a better method of editing the code so we are not directly changing the code in the module until all changes can be inserted at the same time. It will also support cleaning up the code as we make changes, such as removing extra spaces and lines or adding lines without needing to worry about the declaration start and stop indices being off. Depending on variable circumstances, it may also support execution analysis.
No due date•5/13 issues closedFirst minor update of 2.0
No due date•55/90 issues closedThis version will include source control (GitHub) integration, WPF controls in dockable hosts, many more refactorings and inspections, and lots of bug fixes.
No due date•565/566 issues closedThe next version of Rubberduck! Will support hoards of bug fixes, Git source control, new refactorings, limited language localizations, and much more! Stay tuned for updates!
Due by June 14, 2015•125/125 issues closedThis release will focus on improving performance and general user experience, as well as expanding our test coverage and fixing any bugs found in the v1.2 release.
Due by March 22, 2015•24/24 issues closedThis version brings us a rebuilt grammar/parser, and a new strategy for locating identifiers and references to identifiers; this enables fixing a number of code inspections / false positives, but also introducing new ones (inspections, not false positives! ..well hopefully at least...) all while improving inspection performance. It also includes a full-fledged "rename" refactoring, as well as new navigation tools that leverage how easy it is becoming to locate identifiers and their usages.
Due by May 3, 2015•43/43 issues closedThis milestone is for features that are on the roadmap, just not for next version yet.
No due date•27/46 issues closedThis version includes massive changes to the parsing strategy, and a few of the perks that these changes enable.
Due by March 1, 2015•77/77 issues closed- No due date•8/8 issues closed
RubberDuck needs a Setting/Options dialog for any configurable items. Nobody wants to edit XML config files by hand. The settings dialog should provide a familiar UI by mimicking the options dialog of Visual Studio. * TreeView Control on the left to provide access to different groups of settings. * Selecting a TreeView node should activate the control related to that setting on the right. * One control per <UserSettings> group.
No due date•16/16 issues closed- No due date•9/9 issues closed
Using a tree structure representing the code, Rubberduck will be able to inspect VBA code and make suggestions on naming and code constructs being used, recommend refactorings and point out issues such as dead code, unused variables and members, etc.
No due date•13/13 issues closedRubberduck will provide the ability to create "test modules" and "test methods" within them, and a "test explorer" tool to view, navigate and more importantly execute unit tests.
No due date•10/10 issues closedRubberduck will empower certain specific comments (configurable) to become "todo" items, and the add-in will provide a way to view and navigate these items (`'todo:`, `'bug:`, `'note:`, etc.).
No due date•5/5 issues closedRubberduck needs to *understand* the code, in order to analyse it; the parser translates VBA code into a tree structure, with various types of nodes. Use this milestone for all issues related to parsing VBA code.
No due date•15/15 issues closed