[Yum-devel] Sqlite improvements

seth vidal skvidal at phy.duke.edu
Mon Jan 24 22:23:59 UTC 2005


On Mon, 2005-01-24 at 17:22 -0500, Jeremy Katz wrote:
> On Mon, 2005-01-24 at 16:50 -0500, seth vidal wrote:
> > > Seth: Any chance of starting a branch for the sqlite work or is 2.1.13 
> > > due any day now with the sqlite patches going into HEAD straight after that?
> > 
> > Yes - I think it should be possible - I'd like to keep the patches to
> > that branch limited to sqlite changes, though.
> > 
> > To be honest the sqlite changes should only ever affect the yum module
> > section and nothing of the cli application code.
> 
> How about an alternative plan?  What's currently in CVS and in 2.1.x
> could very easily be considered "stable" at this point.  Perhaps not API
> stable, but feature stable, which is more important to the majority of
> the userbase (imho).
> 
> So what if 2.1.13 becomes 2.2.0 and you branch off a 2.2 maintenance
> branch.  Just for major bugs that need fixing, I wouldn't actually
> expect a lot there.  And then, continue using HEAD for some of the
> things like sqlite and some of the API work that's going to be needed
> for the graphical interface.  And other crazy things :)
> 

Since a lot of the changes in cvs at this momemnt - how about 2.1.13
stays 2.1.13 - is released and minor changes made to become 2.2.0 after
that. I'd just rather 2.2.0 not be a paperbag release :)

And then we do as you've suggested?

-sv





More information about the Yum-devel mailing list