[Framework-Team] Re: [Plone-developers] Plone 3.2 and 3.3 planning
Previously Martin Aspeli wrote: > Discussions will happen regardless, of course. Maybe we should make some > intelligent use of the sprint time to connect the FWT with PLIP authors > for some workshops/brainstorming? > > Should we just put this to a vote? I think the main impact here is on > the current FWT (especially since Wichert regrettably won't be at the > conference), so IMHO it should be up to them. The most important thing that I want to happen is to be absolutely sure that PLIPs are reviewed promptly. Since almost the entire framework team will be present at the conference I think it makes sense to take that opportunity to get them to work together in reviewing the PLIPs and possibly discussing their internal procedures as part of that process. Hence the deadlines I set. If people write PLIPs during the proposal and the framework team is willing to include those in its review work than I have no problem with that. There is even room for that since the review deadline is set a week after the conference (I was expecting this response). I'm not willing to move deadlines for it. > As a data point, I'm in the same boat as Limi. It's extremely unlikely > that I'll even have time to think about any PLIPs until the conference. > My life's pretty much on hold due to work until then. Obviously I don't > warrant an exception or special treatment (nor does Limi), but I > wouldn't be surprised if other people had similar ideas. As a data point it seems neither of you have ever written a PLIP during a conference, which is perfectly understable: both of you are way too busy preparing your talks, talking to people, organizing various and socializing. That was true of previous conferences and will be true for this one as well. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: [Plone-developers] Plone 3.2 and 3.3 planning
Previously Alexander Limi wrote: > On Thu, 11 Sep 2008 00:50:44 -0700, Andreas Zeidler > <[EMAIL PROTECTED]> wrote: > > > so personally i'm still undecided and would like to hear some more > > opinions. spontaneously i think i'd rather "leave the window open", > > but i'd like to contemplate about it a bit more... > > Please leave the window for PLIPs open until after the conference. Most of > our best thinking happens at conference sprints, and that's the part that > you can't replicate anywhere else — once the PLIP is written, you can > pretty much work on it anywhere, you don't need a sprint for that > (although it does help with blocking out time). My memory made me think PLIPs are generally not written at conferences so I did a bit of analysis on the creation date of all PLIPs on plone.org. That showed that are definite peaks in PLIP productivity but they do not match with a conference at all. The latest big peaks are December 2007, August 2006, March 2006 and December 20205. All other months only show 0-3 PLIPs while each of those peaks is >10. With this evidence I'm even more convinced that it makes more sense to ask people to create PLIPs now and let the framework team disucss those at the conference, providing immediate feedback to the PLIP authors. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: [Plone-developers] Plone 3.2 and 3.3 planning
Previously Martin Aspeli wrote: > Wichert Akkerman wrote: > > We need to get Plone 3.2 and 3.3 on the road. Contrary to previous > > releases I am not going to produce a complete schedule for the whole > > release process this time around - we've seen too often that those > > schedules keep changing anyway. Instead I'll keep planning the next two > > steps in the process for each release. > > That sounds like a good idea. > > > Lets start with Plone 3.2. This release will be a maintenance release > > for Plone 3.x in all aspects except packaging technology: it will be > > fully egg based. The first two steps for this release are: > > > > * egg releases of all components ready before October 1st > > * first alpha release during the Plone Conference > > We also need to determine what we do with existing eggs that have > dodgy/missing dependencies, and whether or not we can make > plone.recipe.plone optional (or just a dumb wrapper around zc.recipe.egg). We already have some suggestions and discussion on that and I have a local git tree which tries to solve a lot of this. I'll commit that back to svn after my vacation in a few weeks. > > For Plone 3.3 we will start with a round of PLIP previews, during which > > the framework team can provide a verdict on the desirability of proposed > > PLIPs. The criteria are correct technical design, correct user interface > > design, and the need merge the PLIP in core instead of maintaining or > > maturing it as an add-on. The dates are: > > > > * PLIPs to be submitted before October 5th > > * framework team gives verdict on all PLIPs before October 20th > > I assume this is about PLIPs in principle, rather than code/bundles? > > I think we need to give people a bit more time if we're talking about > code, especially since we want people to help with the 3.2 work (and > testing!) as well. This is not about code at all, it is about deciding early on if the PLIPs are desirable and correct so we can immediately inform the PLIP authors. I don't want people working very hard at a PLIP when we already know that it will not be accepted or that it will need to be changed. > > The planning is geared around the Plone conference; I am hoping that the > > framework team will be able to take schedule one or more discussions > > there to discuss these PLIPs, if possible with the PLIP authors present. > > That's a good idea. On the other hand, I wonder if it would be nice to > give people a chance to come up with and work on PLIPs during the > post-conference sprint. In the past, we've seen a spike in PLIPs around > sprints as people focus on one thing or another. > > I think it'd make sense if the current Framework Team could decide > whether they'd prefer to have the PLIP deadline, say, on the Friday > following the conference (October 17th) with this in mind, or if they > would benefit more from having time to discuss PLIPs at the conference > and thus keep the deadline for the 5th. There is always a reason to wait for another date. I think a lot of people are coming up with ideas while preparing / psyching up for the conenference, so this schedule makes sense to me. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
