INN 2.3.4 out the door

[Alex Kiernan]

Russ Allbery <rra at stanford.edu> writes:

> The Doctor <doctor at doctor.nl2k.ab.ca> writes:
> 
> > Happy New Year.  What is left for 2.4 ??
> 
> Almost nothing.  We're basically there.  The only big thing I have left
> pending is to decide what mechanical changes we want to do before the
> release and make them, and then make sure everything is still working
> afterwards (I'll likely upgrade my local news server to the latest
> snapshot again, for example, to make sure it works as expected).
> 
> We may do a bit more patch review and merging if there's time; I have a
> patch for innfeed to feed backlog first that was submitted a long time ago
> that I'd like to get in, since I think it's fairly self-contained and the
> functionality is controlled by an option.  But unless Alex has more stuff
> he wants to merge for the release, I think we can hold off on any other
> major changes until after the release.
> 

Very little, the only stuff I've not got committed are:

some changes to tradindexed to check for ESTALE at judicious points
when you're nfs reader (and the new tradindexed code is so nicely
structured, that the changes are very non-invasive)

the binary search code to select the start point for newnews (which I
was planning on waiting for discussion on changes to the overview API
before I tried to commit it - right now its implemented as a magic
global variable which nnrpd and tdx-data are intimate over)

some changes to the nnrpd msg id cache code to make it more effective
for clients which issue a string of HEADs followed by a string of
BODYs

Do you have any dates in mind for a release?

-- 
Alex Kiernan, Principal Engineer, Development, THUS plc