On Fri, Jul 31, 2009 at 06:10:52PM -0500, Shawn Walker wrote: > As an FYI, my plan for implementing the new catalog format is roughly as > follows, split by phase: > > Phase 1 > ======= > * copy common catalog code into server/catalog.py and change it not > inherit from pkg.catalog (to avoid the server being affected by client > changes in the next phase) > * nuke rename code wherever it lives > * send out for review and putback > > Phase 2 > ======= > * implement catalog v1 format client-side only, without the ability to > perform catalog/1/ operations (the client will retrieve v0 catalogs and > then transform them locally) > * send out for review and putback > > Phase 3 > ======= > * implement server-side catalog v1 changes and client-side catalog v1 > retrieval > * send out for review and putback > > ----------- > > Splitting the implementation into phases above should: > * make review easier > * get more testing and ensure v1 catalog clients can retrieve and > transform v0 catalogs properly > * allow better coordination with transport changes > > Feedback appreciated.
Sounds reasonable. It would help me figure out when I need to get my bits done if you were able to outline your transport dependencies for the different stages. I haven't had as much time to focus on this in the past week or so due to 10107, but I'm hoping that I'm close to wrapping that issue up. -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
