Re: [Etherboot-developers] latest greatest eboot with IDE boot

[<ke...@us...>]

>And could we distinguish between what makes a release canidate and what
>makes a development release?

For me a RC is just a snapshot and doesn't have any associated tag in
CVS. If bugs are found in it, good, we fix them and make another RC. A
release (development or production) is entered into the Sourceforge
release page and gets distributed to mirrors. I make announcements to
Freshmeat and a couple of other places. Marty makes an rom-o-matic
version. If bugs are found, they go into the patches page and are held
over for the next release. So a release is a big step.  Hopefully it's
just the final RC with the version number changed.

>You delayed initially because there wasn't a multicast client, but I
>have fixed that and a couple of other things.  I am pretty certain
>etherboot is over the major hump and headed for another stable
>release.

Ok, before we do that I'd like to do regression testing and also to
check that the new features work. I guess though that for a development
release the audience is different. Or should be. You will get the odd
newbie who will ask how come it says gcc not found.

I'd like to make the release 5.1.2 and then when all the legacy
implications are understood, release it as 5.2.0.