| Re: [cf-dev] Californium 1.0.0 |
|
Hi all Unfortunately, I only found time now to work on the open issues that should be closed for 1.0.0 (many Matcher state and
clean-up for blockwise transports). For some of the things planned I am missing either feedback/submissions (API and error handling) or time (proper design for alternative transports). Kai, what is the status of Scandium for the release? Wayne, I am quite lost in all the Web and wiki pages that branch out from the link you provided. Most of the information
is apparently already in place or generated automatically. Is there a clear and concise list what I have to do? Following the list in the wiki, I just killed existing information on the project Web site, as the release record is apparently the same thing as
the release plan information on the project Web site… :S Can you please help me with that and hopefully undo this? Ciao Matthias From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Hudalla Kai (INST/ESY) Hi Wayne, you seem to keep a sharp eye on the projects‘ release plans
J In this case, I have to admit that we failed to update the project web site to reflect our updated release plan we came up with during a recent phone
call. @Matthias: I have updated the release plan on the project web site setting the release date to Aug 31st according to the minutes you
posted to the mailing list. I have also scheduled an M5 milestone for end of July in order to re-align all components to the same milestone level and incorporate any outstanding PRs. We should then start to schedule the review process for the 1.0.0 release
because we will probably have to do some homework (e.g. regarding documentation) Regards, Kai From:
cf-dev-bounces@xxxxxxxxxxx
[mailto:cf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Wayne Beaton Greetings Californium! -- |