On Tue, Jan 25, 2011 at 10:01 AM, Gary Poster <[email protected]> wrote: > Hi Robert. The people with more YUI 3 experience on my team have warned me > that jumps from one "big" version of YUI to the next--say, 3.1 to 3.2--can be > very disruptive. They compared them to Python major dot releases. > > 1) Are you responsible for scheduling the YUI upgrades? If not, and no one > is officially, I suggest that we find someone to take that responsibility.
I don't have it on my 'things to check plate'. I could add it, or we can do it when useful in the same way we upgrade our zope dependencies - that is when someone wants something, we check the impact and do the upgrade. > 2) For whoever will be responsible, what will our upgrade policy be? I'm > interested in how it will be announced to the team and what kind of lead time > we should expect. Perhaps others will mention other things to consider. I don't know :) What do you think we should do here? My initial thought is that staying up to date on YUI has significant benefits for us. > As you know, I'm also interested in the Python upgrade story, and > coordination for a smooth transition to the next LTS. I expect the Python > 2.7 migration is just another feature card that needs to have its scheduling > negotiated with Jono? I think its reasonable to treat problematic dependency changes as feature cards for the feature queue. Not all important-dependency changes will be problematic or big enough to need a timeslot reserved like that. -Rob _______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
