Hi All, Sorry for the silence... I've been on vacation this past week and just finally got around to catching up with email (by which I mean deleting 300 spam messages).
I think I agree with what most of you are saying. I think the top priorities should be to get 0.8.14-stable out (I think it's pretty much there, we just need to release it), and get the 0.9 branch to a stable state. IIRC, someone mentioned that Ajax works on dev.ilohamail.org but not in CVS, so if anyone has time, I can just tar up the code that's running in dev.ilohamail.org and hopefully the appropriate diffs can be extracted and checked in. >We certainly have to focus on getting a more stable of 0.9. That is why I >thought about introducing a new branch (testing) that will be the place >for new features. 0.9 should be frozen and made stable. With regards to branching, I'd recommend a feature freeze on 0.9, concentrate on getting 0.9 stable, then branching (as 1.0, perhaps?) to add new features. But, personally, I'd like to see 0.9 out the door before new features go in. A few administrative things that I need to set up are: 1. Who needs/wants access to the current blog? 2. Who should messages from the website contact form go to? (There should be multiple people.. I'll just setup an alias) 3. Should we setup a core mailing list at this point? (I think last time we decided to wait, but I think we've waited long enough if we are going to setup a separate mailing list). Thanks everybody, and Happy New Year! Ryo On 12/29/2005, "Martin Waschbüsch" <[EMAIL PROTECTED]> wrote: >Am 28.12.2005 schrieb "Andrew Alderwick" <[EMAIL PROTECTED]>: > >>I'd like to make a point, if I may: there does seem to be a patching >>problem. Reporting bugs is obviously a critical task when improving >>Ilohamail, but it needs to be followed up by a swift patching process. >>The wiki contains ten or so suggested patches from earlier in the year. >>I assume that none of these haven't been committed, otherwise the wiki >>should have been updated. However, some of these patches are still >>relevant and need to be attended to. Similarly, on the mailing lists >>we've had several users ask about 0.8.14-rc3 which claims that it's >>-rc2 on the login screen. This bug is very trivial to fix yet hasn't >>been dealt with. (I suppose that the -rc3 Release Candidate, minus that >>typo, is ready for a proper release by now and can be simply called >>0.8.14.) > >I agree with that. It should just be named 0.8.14 and we can focus on >getting a 0.9 based version to be stable enough for rc1. As for handling >bugs, it is very important that people see they are being addressed. >Otherwise they will get fed up and stop using it. > >>We also need to draw more attention to the unstable releases. The last >>unstable release was in April, and several new features are available in >>CVS. The last thing I want to see is an ordinary user inquire about AJAX >>or something, and to be told "it's in CVS." Things break in CVS - in >>fact, if a program's CVS is fault-free than something is very wrong! >>Seriously though, users require a more high-quality, stable program than >>what is directly available in the versioning system. One of the highest >>priority tasks for the unstable branch is to produce a new semi-stable >>snapshot. I'd be happy to download and use it (which is not the case >>for CVS) and drill out any prominent bugs. > If you compare >it to 0.8, it has many new features that, if they were working really >reliably, would make everyone happy, I guess. > >>I'd love to take on more responsibility than that, but the PhD is too >>demanding :-(. Sorry to level these criticisms when there's little I >>can do to help, but I'd love to see someone turn this around into >>something positive! > >That is why I left good enough alone and did not persue a PhD after my >M.A... *g* > > >Martin > >-- >"What a fool believes he sees, no wise man has the power to reason >away..." > >Doobie Brothers (1978) > > >------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. Do you grep through log files >for problems? Stop! Download the new AJAX search engine that makes >searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >http://ads.osdn.com/?ad_idv37&alloc_id865&op=click >_______________________________________________ >Ilohamail-devel mailing list >Ilohamail-devel@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/ilohamail-devel ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Ilohamail-devel mailing list Ilohamail-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ilohamail-devel
