Since 4.x has been a rather lonely ride for me so far there aren't many open 4.x issues in the issue queue because most of the stuff evolved in my head and didn't really make it to the issue queue but turned into code directly. This should change now. Mostly because we now got Matt Smith (@splatio) on board to help me get this thing out of the door but also to maintain a roadmap in general.
Furthermore, Nico Grienauer (@grienauer) will help us to overhaul the Omega logo (note: We will make sure it is still recognized as the Omega logo). There is currently work going on at CTI Digital (@splatio's company) to prepare a nice, simple Omega Subtheme that we are going to include into the package as an example subtheme which we will probably be referencing a lot in the Documentation for 4.x. We will make sure that that subtheme is 100% lean, well structured, fully responsive, good looking and compliant to the best practices and coding standards in every regard. It should be the go-to resource for looking at "how-it's-done (TM)".
Documentation - General Information
Documentation is always a work in progress. We have established a systematic process for developing quality, consensus based, thorough documentation. If you are interested in participating in future documentation sprints, please join us in IRC to voice your interest. Our sprints are conducted in IRC so if you need help getting plugged into IRC read: http://drupal.org/irc. Anyone interested in helping with documentation should ping @banghouse in #drupal-omega on IRC. A 4.x documentation sprint is currently being organized and is tentatively set for Feb. 6th 4pm (EST).
Documentation - The Handbook
We will have 100% documentation coverage before we get to a Release Candidate... Yes, not a final release, a release candidate. We will be using our existing drupal.org handbook for this. The next sprint will intend to establish an intro level guide to getting started with 4.x. If we have time and energy remaining we may get into more intermediate and advanced level topics.
Documentation - The Project Page
The current project page is outdated. It doesn't reflect the work we've done for 4.x. It needs to outline the path we've taken for 4.x and link to resources such as the 4.x handbook for more detailed information.
The project page should focus on 4.x and only link to the 3.x resources and general information about 3.x in a footer section. We will completely remove 3.x from the project page upon the final release of 4.x which will only happen after the Omega Tools module is fully finished and contains an optional Sub Module which adds a GUI to generate page templates. Until then, we will refer to 3.x as the starting point for people without any HTML / PHP knowledge or no desire what-so-ever to touch code at all.
For now, we will keep 3.x at the top but reduce it down to a minimum and keep it simple. Right below that we will have a section that explains the goals for 4.x and the Roadmap towards Beta, RC and Release. We will also use that to link to major issues.
Documentation - The readme's
Each directory is to contain a readme with basic information about what is contained in that directory and helpful tips for customizing the theme.
Open tasks & release blockers
#1744592: [META] Omega 4.x Documentation
#1900998: Overhaul the project page
#1730090: Slick Omega Logo
#1902476: Entirely override Core and major Contrib module CSS and Templates to comply with modern standards
#1902464: Rethink layouts and how to integrate them seamlessly with Drupal and contrib modules
#1901562: Currently 'drush osub' & 'drush owiz' always enable / set the default theme on the current site even if placed elsewhere.
#1627478: CSS preprocessor order conflict
#1902468: Create a neat Omega subtheme and include it in the package as best practices resource and for referencing it in the Handbook