On Mon, Jul 12, 2004 at 11:24:58PM +0200, Filip Navara wrote:
Mark IJbema wrote:
As i said before i like it best when each release has one distinguising feature (even subreleases). The obvious feature for 0.3.0 would be networking, so even though it would be nice that say SEH works (which i understood is really sweet, but says nothing to end users i think) and that openoffice works, i think we should bring it as the big networking release.
Agreed. BTW, according to my knowledge SEH already works, just we don't use it for the system calls yet.
So imho 'networking' should work. So a user should get the feeling networking works. So for this above mentioned apps which should work:
-firefox -cvs rather define a set of clients here, if tcp/ip works cvs should work, but of course not every client will, so maybe limit it to cvs commandline, wincvs and tortoisecvs?
I'm unsure about pushing TortoiseCVS for 0.3.0. Not matter how much I like it, it's a shell extension and it might require a lot of work.
Ok, i didn't know that, if that's true then we shouldn't try to.
I'm missing email here (second most used internet application?), so maybe we could add thunderbird as well?
Why not postpone this to some 0.3.x release? Of course if we will have Firefox running, Thunderbird is only a small step, but as you said we should concentrate on one bigger feature.
It's because of the bigger feature thing. I'm trying to think in a dumb-user kind of way here. Our next big feature is 'networking'. Now what comes to mind with networking: Internet (and smb shares maybe). What is internet? WWW, email, and ehm... irc and some other nerdy stuff. It's no hard demand in any way, it's just that i'd say it would be better to have it all in one. Of course if it means a lot of work we shouldn't, but i don't think it does (otoh, i'm not really the one to know).
So in short: feature: networking what does the user expect: WWW, email, irc (or actually msie, msoe, mirc)
(msie would be nice for 0.3.1 btw >:) )
[snip]
All other applications working (like openoffice) would be very nice, but i don't see why it should be a goal for 0.3.0.
<kidding type="slightly">Why not make OpenOffice working before 0.3.0?</kidding>
That might be just as good. I don't think OOo justifies it's own direct subnumber, so wether it would be 0.2.5 or 0.3.1 wouldn't realy matter imho. I do think however we need a appealing feature for 0.2.5 (or will 0.3.0 be the following version already, as far as i understood networking would be september/october or so, has this changed?)
Mark