[Cerowrt-devel] freezing cerowrt-3.3

Dave Taht dave.taht at gmail.com
Tue May 1 04:19:58 EDT 2012

Based on the sudden interest in building cerowrt, and my threats to freeze
'later this week', I figured I'd freeze tonight just to keep you on your toes.

While some dig the 'branch' facility in git - I do use it myself - I think it's
saner to have a separate repo name for each major branch. So I renamed
several repos tonight. After a linux 3.4 or 3.5 (there isn't anything in 3.4 we
need so...) process starts up, we'll start a 'next' set of repos.

I'm certainly open to discussion as to how
and what to do with development moving forward, but I'd really like to
have something stable enough for your mom and dad to use day to day,
and move on to focusing on some narrow problems like aqm development
rather than "tracking and fixing the whole universe".

So... *my* intent is to only push major bugs fixes and fixes for
CVEs (security violations) into these repos,

For a while, anyway.

you will need to edit your .git/config for your copy of the
cerowrt-luci and ceropackages repos to append a -3.3 to
point to the right renamed repos on github.

I have also frozen the copy of the openwrt package database:

git clone git://github.com/dtaht/cerowrt-packages-3.3.git

You will want to edit your feeds.conf to point to that rather than 'packages'.

As freezes go, this is still kind of a dairy queen kind of soft freeze,
there's a couple things left to land.

I have pushed out the current patch set for 3.3.4-4. While I continue to
battle bug #379 I'm pretty happy with it under normal use.

Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608

More information about the Cerowrt-devel mailing list