> Philip and I were just chatting about the 1.8 release and where we are > on that. For a thought experiment, we asked, "can we ship trunk > today?" The answer was "no" for three specific items: > > * local moves are kinda broken (thus: fix or roll back) > * svnrdump does not work over ra_serf (move to Ev2 replay) > * --symmetric should be marked as experimental > > We felt that with the above three high-level items handled, then we > could actually ship trunk as 1.8 (with a caveat of a few issues here > and there). > > Can anybody think of additional high-level things that would keep us > from shipping trunk *today*? > > Can/should we focus on fixing these and shipping sooner rather than > later? Are there items that should/must go into 1.8 that aren't on > deck today?
I wasn't able to take a fresh checkout of trunk last night and build on my RHEL5 test box. My 1.7.x snapshot builds fine with neon on this same box, but getting the developer build to notice serf seems almost impossible in this (older) environment with few packages installed. svn co https://svn.apache.org/repos/asf/subversion/trunk svn_dev cd svn_dev ./get_deps.sh sh ./autogen.sh ./configure --prefix=/usr/lfs/v0/apps/subversion/dev \ --without-berkeley-db \ --with-apxs=/usr/lfs/v0/apps/httpd/2.2.22/bin/apxs \ --without-swig make This builds, but does not include serf. Adding --with-serf does not help. get_deps downloaded serf 1.0.1, it appears to have built, just not used. Didn't find anything interesting in the build logs yet. Also, specifying --without-apxs does not correctly disable building mod_dav_svn and mod_dontdothat. The build fails with a missing httpd.h, error, so I pointed it to my local build of httpd as a workaround. Have I missed some important step? I'm sure this is just my ignorance of setting up the dev environment... Another very *minor* thing I noticed is that the sqlite3 error during the build still references the old sqlite3 naming format and references a http:// URL that is no longer valid. Kevin R.
