MidnightBSD Developer Journal

 There's a preliminary release on the FTP server now.  I haven't gone through full testing yet, so avoid it until the developers get through testing the ISOs.  I'll post release notes tomorrow.

Only i386 is up at this time.   If everything goes according to plan, amd64 will be built in the next week.  It will take at least 2 days to build packages and I've had to use that machine for i386 work.  I haven't made a call on sparc64 yet.  

Please tell me if package symlinks are bad on the ftp or files that shouln't be there are there.  I've tried to go through and remove restricted ports and ports listed in mports/LEGAL, but i might have missed something.  It's late and I'm tired.

 and i found a problem with the ISOs.  I'll generate new ones tomorrow.  The packages aren't included correctly.

Due to my snafu with sysinstall, 0.2-RELEASE has problems installing packages.  I could kick myself for not testing this properly, but it happens when you're drinking and coding.  

Here's the new schedule:

i386

We'll have 0.2.1-RELEASE ready for i386 in the next few days.  I'm not going to rush testing it this time just so we can be "done".  I've already created some patches to fix the above mentioned problem and am building a test snap with packages to verify.  If that goes well, I'll tag 0.2.1 and do the final build. 

amd64

This can't be started until 0.2.1 is done for i386.  I'm hoping mid-week, but I start getting busy on Wednesday.

sparc64

While I haven't made a final decision on this, I decided to start updating one of my sun machines to 0.2.1 so that I can build packages.  It usually takes a week with 3 machines on magus and I've only got one setup at the moment.  If my second machine and ctriv@'s comes into play, the earliest would be Friday.  If so, this would be our first sparc64 release.