I put together a second release candidate for DragonFly 3.8, and it’s uploading now. The reason is that I goofed up the pkg build – Sascha Wildner has hopefully made that harder for me to screw up now.
Release is still planned for the 4th.
I put together a second release candidate for DragonFly 3.8, and it’s uploading now. The reason is that I goofed up the pkg build – Sascha Wildner has hopefully made that harder for me to screw up now.
Release is still planned for the 4th.
Comments are closed.
There seem to be a lot of open tickets for the release still, I’ve never managed a release schedule of anything so I’m not talking from a background of experience by any means, but would it be bad if we waited until more of the bugs were worked out, there’s 63 bugs still listed open for the release. It seems like if we release as is on the 4th, that we’re admitting that we know there are 63 active bugs in the release, and that just seems weird to me.
Some of these are bugs that aren’t yet reproduced; some are possibly already solved, some are not realistic to get done in this release timeframe (update pf, for instance), etc.
These are all bugs that were arbitrarily linked to the release; none of these (that I know of) are common problems.
Will there be GUI versions for the release?
Dunno – I haven’t even tried building them, and there hasn’t been any work on them since last release and the switch to pkg. It requires someone who’s really interested in it to organize and build it.