Release process

[Ted Bullock]

I just want to make a couple comments about the release process for
httperf that I think will work.

I am not actually a very great fan of "branching" if it isn't really
necessary. Maintaining code between various branches has always
occurred as a pain in the ass to me, a much much cleaner approach is
to do all the development on HEAD, and as the time for making a
release approaches, create a tag HTTPERF_XYZ_BASE (where XYZ is the
release number) then we spend the next week or so doing testing, then
when we're bored with that, we tag the code HTTPERF_XYZ_RELEASE,
bundle it and release it.

This way the attention always stays focused on the head of development
and doesn't get distracted with

--
Ted Bullock <tbul...@comlore.com>

[Martin]

I realize having a lot of branches would be a pain. The reason I
would like to see two is I want to be able to fix bugs (and possibly
add a few new features) on the "original" core, while the "new" core
is developed, tested and stabilized. I don't see how to do this just
with tags. if I'm missing something, please clarify.

thanks

Martin