Hi all, I agree with Reto regarding the shortening of the artifacts ids, but this is going to be a huge work and maybe we should set a "code freeze" for a couple of days while doing this name refactoring or make this work in a branch (maybe better). I think we should point out the list of issues to be closed in a couple of weeks and defer everything else past the release. This is my short list of must-fix issues:
- CLEREZZA-245 - read/write locks are not set in different projects - CLEREZZA-215 - Triaxrs: jaxrs resources/providers are not bound after the first start, because their reference is static - CLEREZZA-206 - test failures in org.apache.clerezza.rdf.jena.tdb.storage >From what I see on ohloh.net Clerezza code analysis [1], I think a significant part of the release process will be also verifying the code and dependencies' licenses. My opinion regarding the writing of a tutorial is that we should work on it just after we have a release so that people can get Clerezza artifacts from a repository and/or download a distribution to play with. The release will also force us to have a clean working build process we can then document on the tutorials so that people shouldn't find so hard to just do a 'mvn compile'. Cheers, Tommaso [1] : https://www.ohloh.net/p/clerezza/analyses/latest 2010/6/28 Reto Bachmann-Gmuer <[email protected]> > Another thing: when releasing I think only code from closed issues should > be > in trunk and we currently have a couple of issues which request reviewing > feedback by being in the state "resolved". > > On Mon, Jun 28, 2010 at 2:43 PM, Reto Bachmann-Gmuer < > [email protected]> wrote: > > > What comes to mind is: > > > > - pax-exam: for the test to be of value, i.e. not generate false positive > > (by ignoring overwriting methods) and not failing with local snapshot > > versions we need pax-exam 1.2.1 - On May 31st Toni Menzel said he was > goind > > to do the relase asap > > - sesame: not in maven central -> we can release the non sesame related > > modules > > - triaxrs: there are some cddl files from jersey which need to be removed > > > > Obviously there are many features I'd like to see in clerezza soon, but I > > think we should release early and release often. Also to have a stable > > reeference against which to write tutorials. > > > > It would be nice to have our artifact-ids shortened (removing > > org.apache.clerezza) but this too can be done later (but stability in the > > naming is an advantage) > > > > Cheers, > > reto > > > > > > On Mon, Jun 28, 2010 at 11:41 AM, Tsuyoshi Ito <[email protected] > >wrote: > > > >> Hi tommaso > >> > >> Absolutely agree with you. > >> > >> Probably Reto could create a list of issues which should be fixed for a > >> release candidate. > >> > >> Cheers > >> Tsuy > >> > >> > >> On Fri, Jun 25, 2010 at 7:55 AM, Tommaso Teofili > >> <[email protected]>wrote: > >> > >> > Hi all, > >> > I would like to push for the first incubating release of Clerezza; > >> talking > >> > these days at IKS Workshop with some people made me realize that this > is > >> > going to be one of the first steps to enhance our community. > >> > This is going to be a challenging process but hopefully will lead us > to > >> > have > >> > a cleaner project too. > >> > What do you think? > >> > Tommaso > >> > > >> > > > > >
