For 1.4, I would like to focus more on fixing bugs related to distributed builds.
For 1.5, I would like to see continuum-core refactored. It's all tangled up so it's hard to make any changes without breaking stuff. I once tried to move the mail notifier out of the core but ended up not being able to do so. Thanks, -- Marica On Tue, Jan 19, 2010 at 6:58 PM, Deng Ching <[email protected]> wrote: > For 1.4, I'd also like to improve on the performance when using distributed > builds with LDAP. It is currently taking a while to build and release > projects using this set up. > > Thanks, > Deng > > On Tue, Jan 19, 2010 at 9:15 AM, Wendy Smoak <[email protected]> wrote: > > > On Sun, Jan 17, 2010 at 4:44 PM, Brett Porter <[email protected]> wrote: > > > > > For mine, I'd like the 1.4 series to just focus on frequent problems > and > > usability issues, such as those that Sebb has been so diligently raising > > recently. > > > > > > Concurrently, like Emmanuel, I'd like to start talking about some > > architectural changes for releases beyond 1.5. > > > > Not that I'll stand in the way of people who want to fix stuff, but > > personally I'm unsure whether fixing the usability issues is worth it > > without the architectural changes. > > > > At least, it seems to me that the big problems I run into are caused > > by things that are going to require a change in the data model -- the > > way historical build results are not immutable, and the complicated > > way that parallel builds require you to attach queues to a schedule. > > > > The Continuum code is not easy to work with, and that's an indicator > > of technical debt that needs to be paid back. An example here is... > > I'd really like to change the notification email template, but the > > email notifier is baked into the core. The other notifiers were > > separated, so there must be some reason this one wasn't. > > > > -- > > Wendy > > >
