Proposal: Feature freeze for release

[majenkotech]

Place a freeze on all new features and focus 100% on bug fixing and general cleanup, then release what we have as RetroBSD 1.0

We've never had a "release" before, and I suggest that it's high time we did, Let's get what we have working perfectly and tidy everything up and get an official release out there.

[alexfru]

How do we determine we can release? Are we going to vote or something? Or is there some date in mind?

[majenkotech]

I have no idea ;) Shall we take a vote on it?

I am thinking more a state than a time - when we can all agree that we are fairly happy we have most of the niggles and bugs ironed out (or at least lined up against the wall).

[alexfru]

Agreed. I hope we fix as and ld for real before we release. It looks like there are still some issues, but I need to dig again to figure out what's wrong now and then have it fixed.

[majenkotech]

Do you want to open an issue (or issues) on here for the as and ld problems? That way we can keep track of them.

[alexfru]

Yeah, I could open one. But I first want to do some exploratory work to have a little more than "Help, it's not working!". :)

[majenkotech]

I have created a 1.0 Release milestone. Any issues that want to be fixed before we release should be tagged with that milestone.

[sergev]

Today I created two more branches: 'exec-elf' and 'games'. First one is a merge of patches from karolina.lindqvist: support for ELF format in the kernel. It enables kernel to directly execute ELF binaries, so we no longer need elf2aout utility. This branch is ready for the merge into the mainstream.

The second branch 'games' is a temporary storage for my slow pace work on porting src/cmd/games. Please do not pull&merge yet: I will let you know when finished.

All these changes are not critical and can wait until Release 1.0 done.