Releasing an alpha soon is high on our list, part of our hesitation is that we want major architectural decisions pretty solid as upgrade paths for distributions are much more complex than upgrading a single module. Additionally we want to adequate documentation in place for both usability reasons and to properly educate users about the issues with customising a distribution if you intend to follow the upgrade path of the distribution.
As I see it these are the external blockers for a 1.0 release.
Stable release of og 2.x
Stable release of features
Stable release of entity_reference
Stable release of strongarm
Stable release of views bulk operations needed for managing group membership
Comments
Comment #1
jgraham commentedWe don't have a set date. As soon as its ready ;)
Releasing an alpha soon is high on our list, part of our hesitation is that we want major architectural decisions pretty solid as upgrade paths for distributions are much more complex than upgrading a single module. Additionally we want to adequate documentation in place for both usability reasons and to properly educate users about the issues with customising a distribution if you intend to follow the upgrade path of the distribution.
As I see it these are the external blockers for a 1.0 release.
Internal blockers
Things that are very nice to have;
Comment #2
jgraham commentedComment #3
lightsurge commentedI would add #1535668: update various exportables to support dynamic details related to feature nodes (eg. clubs, teams, etc.) to this mix. Without it, the only time I could use Julio (without patching it) would be with the school that happens to ask for the exact section heading / group headings that come with it.
Comment #4
Taxoman commentedComment #4.0
jgraham commentedUpdating summary
Marking strongarm stable as done.
Adding #1535668
Comment #4.1
jgraham commentedformatting
Comment #4.2
jgraham commentedissue links
formatting
Comment #4.3
jgraham commentedUpdating status of 1.0 blockers