On 30 January 2012 11:26, Ate Douma <[email protected]> wrote: > On 01/30/2012 08:33 AM, Jasha Joachimsthal wrote: > >> On 30 January 2012 02:30, Ate Douma<[email protected]> wrote: >> >> Hi team, >>> >>> The next 0.8-incubating release candidate is scheduled for tomorrow, >>> however I'm afraid I'm not ready (hardly started to be honest) with >>> JIRA-437. >>> >>> And as IMO that issue really needs to be addressed properly before we can >>> tag and create the next release candidate, I've now upgraded that issue >>> to >>> priority BLOCKER. >>> >>> As I expect JIRA-437 will take me at least several hours to complete, >>> requiring many recent new dependencies to be 'cleared' as well as dealing >>> with the shindig situation (missing, incomplete NOTICE and LICENSE >>> files), >>> see SHINDIG-1689, I won't be able to complete this before the planned >>> 0.8-incubating release tag... >>> >>> So, I think we have three options: >>> a) delay the 0.8-incubator release tag a few more days >>> b) someone else chimes in to (help with) complete JIRA-437 >>> c) branch the trunk for a later (this week) 0.8-incubating release tag so >>> work on 0.9-incubating can continue right away in trunk, merging fixes >>> from >>> the branch when they arrive >>> >>> I expect I can get JIRA-437 finished by myself, at least if it doesn't >>> turn up something new/unexpected needing further investigation/actions, >>> before end of this week, hopefully already by Wednesday evening. >>> >>> WDYT? >>> >>> Regards, Ate >>> >>> >> With some help the delay of the 0.8-incubator release can be minimal. A >> branch for only a few days is maybe an overkill if the release can be done >> by Friday instead of Wednesday. >> > FYI: the release date was set to today (Monday), not Wednesday. > Wednesday might even still be possible but I'm in a rather tight squeeze > the next few days so I cannot promise I'll have enough time until then.
Today is not the last day of the month, neither is Wednesday, but tomorrow (Tuesday). > > > Regarding the NOTICE entries that are needed due to the incorrect Shindig >> notice file: can you indicate them in the NOTICE file or otherwise keep a >> list in a separate file so we can remove them easily after Shindig has >> cleaned up its NOTICE file? >> > No, thats not how it works: our (Rave) NOTICE and LICENSE files need to be > fully self contained, e.g. cannot/should not 'delegate' to (future) N&L > files provided for instance by Shindig. If anything, the Rave N&L entries > needed for using Shindig might be helpful for them to fix their N&L files. > So there is nothing to be 'cleaned up' afterwards. Thanks for the explanation > > > BTW you're referring to JIRA-437, but that should be RAVE-437: >> https://issues.apache.org/**jira/browse/RAVE-437<https://issues.apache.org/jira/browse/RAVE-437> >> > Ah, good point :) > > Ate > >> >> Jasha >> >> >
