Review Board 1.1 RoadmapThis describes the roadmap for the 1.1 release of Review Board, including an estimated schedule, features we expect to have in the release, and bugs we want to fix. ScheduleReview Board 1.0 was released on June 20, 2009. Since then, we've had a lot of development, including the Google Summer of Code. We hope to have a 1.1 release by January 2010. This may change due to many factors, but we're proceeding with this goal in mind. The release process will be: - Alpha 1: Most of our must-have features should be implemented.
- Release Date: Saturday, September 19th, 2009
- Alpha 2: All of our must-have features must be implemented. Many of our Milestone-1.1 bugs will still be open, but no new features will be added outside what's on this roadmap without a compelling case. We hope to have most of our contributed patches that are ready to commit in this release. Non-trivial contributions will be pushed to our next release.
- Release Date: Monday, October 11, 2009
- Beta 1: All "maybe" features that we decide we want in 1.1 must be implemented. All other features will be pushed back to the next release. The focus after this will be on documentation and bug fixes.
- Release Date: Saturday, November 14, 2009
- Beta 2: All medium and high priority Milestone-1.1 bugs should be fixed.
- Release Date: Monday, December 5, 2009
- Release Candidate 1: Additional Milestone-1.1 bugs fixed as necessary.
- Release Date: Saturday, December 13, 2009
- Final Release
- Scheduled Release: Saturday, January 23, 2010
Release Dependencies- Django 1.1: Review Board's biggest dependency is Django. Django 1.1 released on July 29, 2009.
- Django Evolution: Django Evolution is another important dependency. Their release schedule is unknown but we'll likely depend on either a snapshot of their Subversion repository or the closest stable release at the point of our release.
Release 1.1Must-Have Features| Feature | Status | | Dynamic update notifications | Committed (ce1eeed) | | Hosting service easy-config | Committed (52c49a8) | | Screenshot drag-and-drop upload | Committed (621f6ac) | | HTML email support | Committed (05a8aeb) | | Raw-file URL remote Git support | Committed (8df8d29) | | Toggling whitespace display in diff | Committed (629bbc1) | | Move detection | In progress | | Repository validation | In progress | | SSH and HTTPS support | In progress | | New settings UI | Not started |
Maybe Features| Feature | Issue Number | Status | | OpenID authentication | issue 242 | Not started | | Incremental expansion | issue 342 | Not started | | "Not Shippable" status | issue 489 | Not started | | Real names in drop-downs | issue 598 | Committed (245ab23) |
BugsWe have a list of bugs we'd like to fix for 1.1. Any and all bugs that we can fix should be fixed, but we specifically mark some as Milestone-Release1.1. Release 1.5Must-Have Features| Feature | Issue Number | Status | | User/group access policies | | Not started | | Third-party extensions | | Not started |
BugsWe have a list of bugs we'd like to fix for 1.5. Any and all bugs that we can fix should be fixed, but we specifically mark some as Milestone-Release1.5.
|
Sign in to add a comment
You should add statistics/metrics to your must-haves. I set up reviewboard for my organization but I've come to realize that they simply won't be convinced of the usefulness of the tool unless they can see the metrics. It's a shame too, many of their problems stem from the fact that the developers don't collaborate on code.
A lot of work needs to be done for that and it simply won't happen for this release. We won't be writing such support until our third-party extensions code goes in.
In the future, discussions should go on the mailing list. We'll probably be turning off comments on the wiki before long.