I hate to say it, but I believe one weeks notice is more fair. however alpha does not mean completed. Alpha means this shit needs heavy testing! there's still alphas, betas, rc's and then a final release to test and fix things. it just means no NEW features.
On Sat, Aug 14, 2010 at 10:14 PM, <vto...@univ-evry.fr> wrote: > Quoting "Carsten Haitzler (The Rasterman)" <ras...@rasterman.com>: > > > On Sat, 14 Aug 2010 18:33:35 +0200 (CEST) Vincent Torri < > vto...@univ-evry.fr> > > said: > > > >> > thought we were about there. i asked - you did not disagree or provide > any > >> > information. what do you expect me to do? i did the right thing. i > asked. > >> > you replied. you gave no list of things you are working on that need > to be > >> > done by 1.0.0 alpha > >> > >> You're always right, of course... I'm fed up, do what you want, as > always. > > > > well if this is how you see it - then not much i can do. there is > > nothing i can > > do in such a situation. you will be upset no matter what is done unless > you > > yourself determine everything, because you didn't share your objectives > with > > everyone else. > > > > you're one of the few people who are actually reliable and > > trustworthy. if you > > don't say you have something to do, i believe it. i'm not doing what > > i want to > > do just because thats how i want it. i engaged the developers - both on > email > > and irc - our primary communication mechanisms - you included. you > > didn't miss > > the emails. you have a whole alpha phase to do things during (as long as > they > > are not breaking api). this alpha won't be perfect. far from it. > > > > but i'm sad to see you upset at me, yet there is nothing i could have > done to > > prevent it as the source of it all is yourself and your actions, so it's > > something you have to come to terms with. sorry. as i said - i trust > > your word. > > you've earned that over the many years. :( > > Yes, I'm upset, because, now, the development is a mess. You, the lead dev, > announce a release (which is great), but you accept that, after that > announce, > plenty of people commit plenty of stuff, with maybe a broken API, not > respecting the implicit naming rule (like in eet, for example... But it's > too > late now for this lib). Cedric finished his changes on edje yesterday (btw, > is > it really finished, tested, etc... ?). > > I would have preferred that kind of announce: > > "Since 2 weeks, the points i mentioned (edje format, etc...) are now in > svn. Do > you guys think that it's mature ? One week for testing and cleaning could > be > sufficient. I plan a release one week" > > Or something like that. And not annoucing the alpha release the day after > the > last commit of cedric on the new edje format. I would have agreed without > any > problem with that kind of announce. We wait for several years for a > release. > One week to check the API and *potential big* problems after such a big > change > like the new edje format is important. > > That's my point of view > > Vincent > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
