On Fri, May 16, 2008 at 2:29 AM, Paul Lindner <[EMAIL PROTECTED]> wrote:
> Hi, long time no commit. > > So I¹m starting the hi5 rebase to trunk now. I¹m also interested in > getting > as many 0.8 features incorporated as possible. Basically I want to commit > 0.8 code to shindig repo instead of committing hackish workaround to my > local repo. > > We should go through the 0.8 changes one by one and open JIRA issues for > any > feature that is not implemented. Perhaps prefix them with 0.8 so they can > be easily filtered. (Alternatively we can create the ³0.8² version of > shindig and just mark all 0.8 bugs fixed in version ³0.8²) I brought this up in an email last week -- I think all 0.8 changes can be implemented while retaining backwards compatibility. If we see anything that can't, we can figure out a way to work around it. The way I see it, these are the major categories of 0.8 items: - RESTful API (in progress) - Gadget spec changes (mostly implemented already, some minor things remaining like inline message bundles) - JS changes (mostly opensocial-0.8, which will be a "new" feature, and a few tweaks to gadgets.* libraries) Cassie -- do you have an itemized list of all the 0.8 changes aggregated? Should we just go from the spreadsheet? For the time being, a separate JIRA issue for each major planned change is probably a good idea to prevent us from stepping on each others' toes. Minor changes (say, anything that can be implemented with less than a 20 line delta or so) should just be committed. > > Regards, > Paul > >
