Comments

Jorrit created an issue. See original summary.

mpotter’s picture

Title: OpenAtrium 2.6.19 release plan [meta] » OpenAtrium 2.6.20 release plan [meta]

Got some of these in 2.6.19. Updating title for next future release.

mpotter’s picture

Title: OpenAtrium 2.6.20 release plan [meta] » OpenAtrium 2.6.24 release plan [meta]
joseph.olstad’s picture

during install, lots of missing theme warnings.
could we also get in this patch:
#2844716-5: "Missing/moved modules" PHP warnings should be PHP notices instead

joseph.olstad’s picture

also, we should use this patch, drastically speeds up installation time.
#997918-29: Menu gets rebuilt continually during install and update (and menu system stores entire, out-of-date theme objects)

update views to latest dev, lots of performance improvements, fixes, regression fixes for 3.18. 3.19 is expected to be tagged soon.

mpotter’s picture

@joseph not sure about the missing theme warnings. Open a new issue for that, but as it says in that issue you linked I'd rather fix whatever is causing the warnings rather than just ignoring the error.

Also, in this issue, please only link to issues in the actual Open Atrium issue queue. This is a meta-ticket showing issues in the queue that should be applied to the next release. If you have a patch in core or other module that you want, create an atrium issue for it along with the appropriate patch to our make files and then also report any testing, performance improvements, etc. Also, Atrium comes with a "Quick Install" process and we recommend that over normal installs, so improving normal install time is a very low priority.

Finally, remember that many modules in Atrium come via Panopoly (views, etc) and we try not to add additional patches unless they are actually needed for Atrium functionality. We also don't usually use "dev" versions of major modules such as Views. But those patches etc should be reported for Panopoly rather than Atrium.