"mini roadmap" for userland for 3.7-dev branch

[Antonio Huete Jimenez]

Hi John,

As I've previously stated, I don't think a roadmap is something
desired, i.e. people should work on whatever areas they want, and not
be "forced" to complete a roadmap. All in all, this is an free
collaboration project as far as I know it.

However, we could create tickets in the tracker with the "hot items"
so that anyone wanting to do the work can pick it up in a easy way,
and work of them if desired.

Best regards,
Antonio Huete

2013/11/20 John Marino <dragonflybsd at marino.st>:
> Another thing I've been hoping (in vain) for the project to produce is a
> real "road map" showing what features are intended for which release.
> Since such a document does not exist and probably will not exist, I
> though I'd start of list of things that I think we should try to
> accomplish on the 3.7 branch with respect to the userland, a sort of
> mini-map for just the current development branch.
>
> Anyone feel free to add items to this list and definitely feel free to
> volunteer to do any of them.  :)
>
> Vendor branch updates
> ======================
> 1) WPA-Supplicant and HostAPD (these are already 3 years old)
> 2) Latest bmake
> 3) Replace binutils 2.21 with binutils 2.23.2
>
> Base compilers
> =======================
> 4) Replace gcc44 with llvm/clang (v3.4) and libc++
> Note: gcc47 will still be primary compiler for foreseeable future.
> clang *might* become the dports compiler at some point.
>
> Other Stuff
> ========================
> 5) Bring in latest iconv fixes from FreeBSD10 (the ones that unblocked
> FreeBSD 10 release), csmapper fixes too
> 6) Check dormant library symbol versioning and switch it on (building a
> new set of packages first as this will break them all)
> 7) Pull in any dynamic linker updates from FreeBSD that may have come in
> over the last 10 months
>
> John