lucene-dev mailing list archives  Site index · List index
Message view « Date » · « Thread » Top « Date » · « Thread »
From "Steven Parkes" <> Subject RE: releases Date Fri, 27 Oct
2006 20:45:16 GMT         not neccessarily ... if somethings in
the trunk, you're saying it should         be included in a
release eventually ... but that doesn't neccessarily need
ot be the 2.1 release ,it might be the 3.0 release  I can see
this in theory, but do our use patterns for svn support it? My
understanding is that trunk is the proto-X.Y.0 branch. If you
start checking X.Y+1.0 or X+1.0.0 stuff in there, it's going to
make creating an X.Y.0 release difficult, right? It's possible
to imagine yanking the stuff out, but the release process just
got a lot more difficult to  The svn model Lucene is using, as I
understand it, is one main branch (trunk) for development plus
patch branches for cut releases (in case patch release are ever
deemed necessary). Only trunk is "actively" maintained: it's the
only thing that gets most commits. The p