New release?

New release?

[Peter Korsgaard]

Hi,

As the eCos 2.0 release is turning 2 years this weekend
(http://ecos.sourceware.org/ml/ecos-announce/2003/msg00005.html), I
was wondering if it wasn't about time with a new release?

A new release would give some nice publicity and hopefully stop people
from wasting time on the ancient v2.0 release, only to later discover
that it was fixed long time ago in CVS.

But what is the status?

It would be nice if the Redhat->FSF assignment could be completed
before the release, but that doesn't seem to be happening?

What about the flash v2 API? Is that getting ready for public
consumption?

Other significant changes since v2.0:

* HAL: A bunch of new platforms
* NET: SNTP, PPP, Improved IPv6 support, IPSEC, LwIP, VNC
* IO: IDE, NAND flash, SPI, I2C
* FS: FAT12/16
..

-- 
Bye, Peter Korsgaard

Re: New release?

[Jonathan Larmour]

Peter Korsgaard wrote:
> Hi,
> 
> As the eCos 2.0 release is turning 2 years this weekend
> (http://ecos.sourceware.org/ml/ecos-announce/2003/msg00005.html), I
> was wondering if it wasn't about time with a new release?

It is indeed.

> A new release would give some nice publicity and hopefully stop people
> from wasting time on the ancient v2.0 release, only to later discover
> that it was fixed long time ago in CVS.
> 
> But what is the status?
> 
> It would be nice if the Redhat->FSF assignment could be completed
> before the release, but that doesn't seem to be happening?

This is the main obstacle at this time, and is a prerequisite. All the 
maintainers are impatient about getting this resolved. It has in fact been 
partially resolved, and what's left to do is (to me) pretty clear and 
straightforward. But it has been very difficult to get a dialogue going at 
all, nevermind momentum. But your mail has been a worthwhile reminder for 
me to prod people to usher the process along, so I've now done so.

> What about the flash v2 API? Is that getting ready for public
> consumption?

I imagine the push towards eCos 2.1/3.0/whatever will be the time that 
gets integrated.

> * NET: SNTP, PPP, Improved IPv6 support, IPSEC, LwIP, VNC

Fair enough, although I don't recall anything significant for IPv5, and 
IPsec was IIRC more a framework to allow future solutions, than a complete 
solution.

Still, more than enough to justify a new release, probably a 3.0 to 
reflect the new IP status. There will be a lot of work before a 3.0 can 
happen though, even after the assignment.

Jifl
-- 
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine