Paul Wong-Gibbs 12:16 pm on January 15, 2011
Tags: Agenda ( 118 )

Next dev chat will be on Wednesday 19th …

Next dev chat will be on Wednesday 19th Jan at 19:00 UTC.

#agenda

Paul Gibbs 12:17 pm on January 15, 2011

I think it would be beneficial if we can (re-)identify what the remaining tasks or tickets blocking the next release are; I’m a bit unclear on what the most important remaining issues are.
- Boone Gorges 4:33 pm on January 15, 2011
  
  From my pov:
  1) http://trac.buddypress.org/ticket/2789 (activation/upgrade/bp-default)
  2) http://trac.buddypress.org/ticket/2600 (root_slug stuff)
  3) http://trac.buddypress.org/ticket/2943 (Component Setup admin panel. If we retool the upgrader so that BP is loaded during the wizard, as reflected by the latest patch to #2789, then we should be able to abstract out the markup from the installer and simply reuse it. In other words, this is dependent on #2789)
  
  http://trac.buddypress.org/ticket/2609 is marked as a blocker, but WP 3.1 seems to be accepting our incorrect way of doing things, so I would suggest that fixing load order is prioritized behind the items listed above.
  
  I know there has been talk about unifying the admin UI, and I see that JJJ has made some commits recently that might help. IMHO this is very important, but we shouldn’t hold up a release very long for this issue alone.
  - Boone B. Gorges 3:03 pm on January 19, 2011
    
    All four of the tickets listed above have been closed in the last few days. Go team!
Boone Gorges 4:28 pm on January 15, 2011

We should discuss WP-BP compatibility issues. Two things –
1) It seems to have been decided that BP 1.3 will require WP 3.1. This seems fine to me, but I would like for us to be explicit about it as a team. Also, we need to make sure that WP 3.1/BP 1.3 release timing works out correctly.
2) It strikes me that the BP 1.2 branch probably will not be WP 3.1-compatible, at least as concerns the Network Admin page (possibly other things too). We can’t simply backport the recent 3.1 compatibility trunk commits if we want to maintain 3.0.x compatibility in the branch. So we’ll need to have a patch for the 1.2 branch that degrades gracefully, and have a BP 1.2.8 ready to drop the day that WP 3.1 is released. Hopefully JJJ can play the role of liaison with the WP core team to make sure that we have a day or two lead-time to make sure 1.2.8 is ready.
Boone Gorges 4:34 pm on January 15, 2011

I will be traveling on Wednesday. I’ll try to get to the chat if I can (via mobile if necessary) but I can’t make any promises at the moment. Thus my verbose comments above 🙂
mahesh 4:44 am on December 8, 2011

We are providing buddypress chat system to over site