On 9/22/07, Radim Novotny <[EMAIL PROTECTED]> wrote: > * at-integration-branch - started by gawel and recently mj did some > changes. Branch seems interesting, because rewrites CMF based > PloneGazette to AT based types. I'v never tried this branch yet. Anyone > using it and knows status?
Yes, I made some initial fixes, but I abandonded the branch, it wasn't in a usable state. We created the attopic branch instead. > * attopic - active branch (PloneSolutions?). Uses ATTopic instead of > PG/Topic. This is what we did next, as using an ATTopic was the most important requirement we had at the time. We'd be fine with merging this with the trunk. > I'v tried to merge into trunk: coplexity-reduction + naro-i18n-fix + > persistent-dynamic-content + attopic + lovely-richreference with success > (most problems were in nl translation), other files merged without > significant collisions. All these branches adds some functionality. Only > one collision is two subscriber search forms. ehm.... I included my > version, but it is not problem to remove it and replace with Florian's > version. Excellent! > I did not include at-integration-branch because types are not compatible > and there is no migration. Most of all, the branch is incomplete and broken. > So, if you are interested in PloneGazette, please vote :) > > Should I commit merged version into trunk? +1 > Should I create another branch ? (review branch) Be bold, make it the trunk. Moving it to a branch can always be done still. -- Martijn Pieters _______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
