This definitely helps. Up to now, I just scanned the list of open issues
thinking about them here and there but rather in the sense of "lets fix
or close it" ;-)
> If yes, I think we should update this list to the bare minimum of
> blocking issues, and add issues for snapshot dependencies that we need
> to get rid of.
Certainly (sounds like wishful thinking ;-) )
Looking at the list of open issues in this query, here are my
assessments of the issues:
SLING-3 Use RequestProgressTracker to log request processing steps
I started adding some tracker entries here and there, but not
completely yet. Functionally and API-wise this may be completed
after the release.
Nice to have.
SLING-147 Add support for org.osgi.framework.system.packages enhancement
Not sure, for now I would say nice to have
SLING-154 Allow access to Node and Property Methods on ScriptableNode and ScriptableProperty
SLING-190 The Sling class of the launcher should verify minimum JDK requirement and fail properly
Nice to have for an initial release
SLING-199 Implement Request Filter management in the virtual resource tree
Has no influence of today's filter registration mechanisms, only
the internal representation and additional support. Therefore
can easily be implemented after the release and probably not a
SLING-247 Provide Scripting variables as request attributes for JSP
SLING-258 ujax.js should define useful constants
Nice to have
SLING-311 Record loaded content to not reload inadvertedly.
Probably nice to have
SLING-53 Add request filter for method overwrite
Probably not required for a first release. I consider this a
"marker" issue to have tracks of, once a real need arises. For
now it is more like just another feature. OTOH it allows proper
method use even through firewall which block HTTP methods except
GET and POST.
SLING-266 Replace old JSON content import by new importer
This is a small one, which just requires a class merge and a
single code line drop, but it has some consquences in that old
JSON import format is not supported anymore. Not
problematic at this time I think. This should definitely be done
BEFORE the release.