Hello Square, Here's my opinion : your email is too long! :p seriously though, it feels long because it's 10h30 AM and I've been in bed for 2 hours trying to sleep and I just can't sleep, so I wanted to check my mails 'quick' before going back to bed and try to finally close my eyes... anyways, you've seen my previous mails, I'm in no position to judge anyone's email lengths :p
ok back to your subject : I totally agree... it IS too slow.. but your idea of bugfix/feature releases will not work.. why? because we've talked about this already a lot.. 0.96 had a huge bug you know... on windows, anyone who pushes the left/right arrows (to modify his text or whatever) in a chat window, actually gets his tab changed.. that's bug, we fixed it a few days/weeks after release and wanted 0.96.1 as a bugfix release for this critical bug... 1 year and 6 months later, here we are still no 0.96.1 and no 0.97... we released 0.97RC1 quite fast and we were happy it didn't take too long.. and 0.97RC1 was EXPECTED TO LAST A WEEK... we never expected to release 0.97 final more than one week after the RC1... oh well.. here we are 7 months later... there's also the bug with the proxies not working in 0.96 and 0.97RC1... still no release.. that's critical you know! all this to say that although we *want* to release fast.. we never do it, simply because everyone is too busy, and because aMSN ate too much of my time so I decided a long time ago to stop managing the project, and since then noone took a step forward in taking that leadership position... You're talking about 0.98 and stuff.. well here's the deal... ok, I'm going to let out a little secret here (probably because I'm tired and I don't think straight)... I know Phil will kill me but well, I don't care at this point... aMSN 0.x is DEAD... finished, I hope that's clear.. that's also one of the main reasons why I haven't been giving it much attention lately.. like all the "can I have this feature" and I say no.. or "fix this bug", and I say "bah, low pri"... simply because 0.97 WILL BE THE FINAL RELEASE OF AMSN 0.x!!! What this means... don't worry, the aMSN project is not dead, but on the contrary, it's moving forward, in July, I started working on aMSN 2. I haven't touched it since August (because of work+school) but it's pretty much good looking so far... rare are those who had the privilege to view aMSN2, I've been keeping in it a private SVN and I didn't want to announce it until it gets usable (full contact list + chat windows working), but since developement is stalled there, the announcement wasn't made... The plan is to release 0.97, then completely stop working on the 0.x branch and start working on the 2.x branch. Anyone who still wants to work on 0.x can do it, so bugfixing, maybe little features added if you think it's a great thing to have.. but the main development team should just move on to working on amsn2. It's a complete rewrite, a different language, and I will NOT say anything more than that... So that's the secret, that's what we've been cooking for you, that's why development is pretty much stalled and that's why there has been no release yet, and that's why we don't need any plans for 0.98 because there won't be any 0.98... I'll have my final exam tomorrow.. after that, I'll probably be busy again but maybe I'll find some time to continue working on amsn2.. then I'll put the source code in the public SVN and announce everything to you guys, and to the users.. so you'll have to be patient.. Ok that's about it.. I don't want to say anything more and I don't have anything more I can say, so I'll end this mail. Thanks Square87 for your concern and trying to find solutions for our release cycle, but as you should know by now, what we *want* is not always what we *can* acheive... KaKaRoTo On Mon, Dec 17, 2007 at 12:03:54PM +0000, square87 wrote: > Hi > I just want to share a my idea. > For me, aMSN releasing is too slow. > I'd like to have the following release: aMSN 0.VERSION.FEATURE.BUGFIX > > I think that we'll never have aMSN 1 but maybe directly aMSN 2, so doesn't > consider the 0 in aMSN 0.etc... > > Think that: > set version $actualversion > set feature 0 > set bugfix 0 > > I suggest: > When we want a new version just decide what that version should have > > if the feature is also compatible with the actual version so release: > incr feature > set name_release "0.$actualversion.$feature" > > if we fix a bug that it's both in actual version and in svn release: > incr bugfix > set name_release 0.$actualversion.$feature.$bugfix > > -------- > For example: > IF in aMSN 0.98SVN we add "plugin manager" and that code is compatible with > aMSN 0.97 so put that code in aMSN 0.97.1 > > IF you find a solution for a bug that it's also in aMSN 0.97: release aMSN > 0.97.0.1 > > If you want to do both things: > but you first add plugin manager and then that fixbug, release: aMSN > 0.97.1.1 > else release: aMSN 0.97.1 > > -------- > I am not saying that for every bugfix release a new sub-version, but we can > do two things: > 1) Release a sub-version every moths. > 2) Release a sub-version when we fix a critical bug, or when we fixed a TOT > bugs, or when we add some feature (with a particular "priority") or > whatever... > > ------- > For example i am writing the code to show notify window with canvas style, > but if i don't have time to do that and it's not a goal for aMSN 0.97 that > code should go in aMSN0.98SVN but if it's also compatible for aMSN 0.97 so > release, after a while, aMSN 0.97.1, without say to users "use svn" that it > could be full of bugs or uncompleted codes or whatever. > > I am saying that because: > 1) we have to compare with other projects > 2) an user cannot wait 1 or 2 years for a new version or download an SVN > that could be unstable. > > Many users use aMSN because we have webcam support but who downloaded aMSN > 0.97RC1 has the $brightness bug that was fixed moths ago... ( seven ( 7 ) > moths ago...). How many people download in 7 moths aMSN 0.97RC1 ? without > considering that it's in the repo of *ubuntu. And How many bugs was been > resolved in 7 moths? and how many thread we have in the forum that talk > about bugs in aMSN 0.97 that they are already resolved? > That's the reason cause i said: for me, aMSN releasing is too slow. > but it's also counterproductive, and in seven moths we doesn't have an > RC2... > > Then i think that have a release history is also a "good imagine" for aMSN. > > Just my opinion. I'd like to have yours. > Sorry for my English. > Thanks, bye > ------------------------------------------------------------------------- > SF.Net email is sponsored by: > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services > for just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Amsn-devel mailing list > Amsn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
