Development update

Development work continues on 1.2.1 and 1.3.


We’re having some build server difficulty, or would have made snapshots available almost a month ago. We hope to have that resolved this week and get 1.2.1 snapshots available so the community can help us test the changes.


We have 1.3 snapshots building but have not had time to put together the required information to make them widely available. We’re also hesitant to provide snapshots of branches that are seeing frequent development and have a number of areas in the midst of significant changes. But once we can write up some caveats, basic guidance, and things to look out for, we will make the snapshots publicly available.

Revision Control Conversion

Bill Marquette has been working on converting our revision control from CVS to git, and replacing cvsweb and cvstrac. These will be much improved across the board once this conversion is complete. Our current systems are less than ideal for a number of reasons. More information on this will come once we get fully converted (ETA unknown).

Share this Post:

10 Responses to “Development update”

  1. Olivier Says:

    Thanks for the news update & good luck with your server and git migrations!
    And don’t forget to enjoy the summer… 🙂

  2. tldstyl3 Says:

    Great news!!!

    Looking forward to 1.3

    Counting the days to its release….


  3. Dave Says:

    Looking forward to seeing your source code management system migrate from CVS to GIT! GIT really works well for distributed development.

    Also looking forward to snapshots of the 1.2 and 1.3 branches.

    Thanks for all the great work!

  4. Chris Buechler Says:

    tldstyl3: sorry, second. 🙂 Moderator delay.

    Git will be very nice for a number of reasons, distributed development being one of them. It also gives us a means of letting anyone create their own branches and contributing code, which we may or may not ever accept into the release distribution which will be restricted to our long time contributors. Frequently people start on something and do not finish it for whatever reason, this will prevent that work from getting lost if someone wants to come along later and finish it. It also eliminates another problem we’ve had for a long time – half finished code in release branches. We want to keep our release branches restricted to only finished work, the release tree should never be broken. That’s essentially impossible to do now because of the limitations of CVS.

    Gitorious is much nicer than cvsweb, and Redmine is vastly better than cvstrac, so it will really offer some significant improvements not just for developers but the community as a whole.

  5. RB Says:

    REALLY looking forward to a git transition. The existing CVS has been a hugely limiting factor in at least my involvement. I’m sure there’ll be a few bumps, but really believe it’s the right direction – way to go!

  6. Southman Says:

    Are we close to getting a look at 1.3 yet?

  7. Dave Says:

    It would be nice to see a publish date on an article like this, so that we know how current it is. The comments are dated, but not the original post.

  8. Chris Buechler Says:

    Southman: As soon as the build system is working again, yeah. We pulled all the binaries out of CVS for a number of reasons, and that necessitated over 500 commits in the past week. It’ll be much better to not keep binaries in release code branches (for one, it means pfSense branches won’t be tied to FreeBSD branches anymore), and is something we have wanted to do for a while, but it’s created a lot of (expected) fallout. As a whole, we have 60-70 man hours into this alone in the past week, and it’s not quite done yet.

    Dave: Err… All the entries are dated. “This entry was posted on Wednesday, June 18th, 2008 at 1:50 am”

  9. Freax Says:


    I think is very important to 1.3 or 1.2.1 to solve the bug related to or integrate a working Frickin package in PFSense.

    Continue the good work.

  10. Chris Buechler Says:

    The PPTP limitation is a limitation, not a bug. It’s that way by design in the underlying software.

    Ermal has been working on something to resolve that issue, not sure at this point if it will be resolved or not.

Please don’t post technical questions or off-topic comments. It is far more likely that your questions and concerns will be addressed effectively through one of our support channels.

Leave a Reply