Bill Marquette wrote:
On Tue, Jul 7, 2009 at 11:27 AM, Tim A.<[email protected]> wrote:
I don't get it. Sure there's a lot of features people want to add. And the
answer is typically, "2.0".
But what is the major platform difference for this major revision?
I just built HEAD (2.0 on 7_2) and... umm... I like 1.2.3, at least it
works.
This is so broken and as far as I can tell, most of its the same anyway.
Why not just add new features / fix things on whats already working so well?
I'm trying RELENG_2_0 now, maybe that'll be more encouraging.
Are you sure you are building from git? RELENG_2_0 doesn't exist in
git, we haven't branched it, it's the 'master' branch. And CVS HEAD
got ditched for a reason...it didn't work, was going to take WAY to
much effort to fix and the 1.x tree worked fine, so when 1.2 branched,
we started calling the new head 2.0. It's a significant change in
that it has full blown user permissions/roles, a fully reworked
traffic shaper, dashboard improvements, and lots of work in DRYing up
the UI (by no means is this work anywhere near complete). I'm sure
I'm missing numerous other items, but it's a much larger leap from 1.2
-> 2.0 than 1.1 -> 1.2 was in terms of features/functionality. At the
end of the day, version numbers don't mean anything anyway, don't get
yourself hung up on 1.1, 1.2, 2.0, we could have just as easily called
1.2 pfSense 6.2 since it was FreeBSD 6.2 based, versions in software
are somewhat arbitrary.
--Bill
Thank you for the explanation, Bill. That clears up a lot.
With "RELENG_2_0", I'm referring to the the builder tools and the
set_version.sh tag, it sets:
RELENG_2_0)
echo ">>> Setting builder environment to use RELENG_2_0 ..."
export FREEBSD_VERSION="7"
export FREEBSD_BRANCH="RELENG_7_2"
export SUPFILE="${BUILDER_TOOLS}/builder_scripts/RELENG_7_2-supfile"
export PFSENSE_VERSION=2.0-ALPHA-ALPHA
export PFSENSETAG=RELENG_2_0
export PFSPATCHDIR=${BUILDER_TOOLS}/patches/RELENG_7_2
export
PFSPATCHFILE=${BUILDER_TOOLS}/builder_scripts/patches.RELENG_7_2
export
CUSTOM_COPY_LIST="${BUILDER_TOOLS}/builder_scripts/copy.list.RELENG_2"
export PFSPORTSFILE=buildports.RELENG_2_0
set_items
;;
It also has a HEAD tag. That built a broken ISO yesterday.
The RELENG_2_0 tag builds a good ISO. I'm using it now on a test
network. And, yea, the GUI looks real exciting..
