Hi,

Am Freitag, den 30.05.2008, 11:44 +0200 schrieb Carsten Ziegeler:
> Ten..nine... ...five... ...two...one
> 
> There's one single issue for a 2.0.0 release in Jira (and it's about 
> docs), so it really seems that we can release next week. :)

We can IMHO deschedule this documentation issue from the 2.0 release and
start cutting the release on monday. If I find time over the weekend to
fix this issue, all the better. But I don't think it is a blocker.

> So I think it's time to ask if there are any outstanding issues? 

https://issues.apache.org/jira/browse/SLING-485 (Replace our JSON
derivate with the original). But I think this has been resolved to not
implement due to the property order issue in the JSONObject. I will
therefore close SLING-485 as won't fix.

> Something we are currently not aware of?

I don't have nothing

> The final question is, what = which parts we want to release? I think 
> there are some bundles/modules which we don't need to include in a first 
> cut.

I would say: api, engine, jcr (api, base, classloader, contentloader,
jackrabbit-*, ocm, resource, webdav), launchpad/*, event, i18n,
httpauth, servlets/*, commons/*, adapter, bundleresource, scripting
(api, core, javascript, jsp, jsp.taglib).

I think, that's about it.

We should split the currently module list in the root pom.xml into two
groups: modules we intent to release and a profile with optional modules
we do not release (yet).

Regards
Felis

> 
> WDYT?
> Carsten

Reply via email to