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 >> > >> > >
