Considering it is one of the primary goals of 0.6, I believe ACL
should be blocker and we shouldn't freeze until it is (actually)
implemented.
> We probably have different ideas of what "feature freeze" means, but
> my understanding is that since it's already something in trunk, it's
> not part of a freeze. But yes, obviously a primary goal of the hack-a-
> thon is to flesh out ACL.
As I see it, a feature freeze is just that. No new features to be added
until release. Finalizing features already in the codebase doesn't come into
count.
Christian
I've created a trac report that returns tickets that include the HAT keyword.
https://trac.habariproject.org/habari/report/10
There's not much there at the moment however.
--
Michael C. Harris, School of CS&IT, RMIT University
http://twofishcreative.com/michael/blog
IRC: michaeltwofish #habari
I've set up a landing page for the Hack-A-Thon on the wiki:
http://wiki.habariproject.org/en/Hack-A-Thon
Each Hack-A-Thon should get its own sub-page, so we can coordinate
developers with potential testers, as well as to keep a running
history of the work accomplished by these events.
Cheers,
Scott