You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(7) |
Aug
(1) |
Sep
|
Oct
|
Nov
(12) |
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(3) |
Jun
(14) |
Jul
(21) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(1) |
Jun
(11) |
Jul
(12) |
Aug
|
Sep
|
Oct
(5) |
Nov
(12) |
Dec
(4) |
| 2004 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2005 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
(2) |
Dec
(1) |
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(2) |
Sep
(2) |
Oct
(8) |
Nov
(3) |
Dec
|
| 2007 |
Jan
(1) |
Feb
(76) |
Mar
(61) |
Apr
(25) |
May
(25) |
Jun
(91) |
Jul
(137) |
Aug
(139) |
Sep
(52) |
Oct
(70) |
Nov
(38) |
Dec
(77) |
| 2008 |
Jan
(225) |
Feb
(91) |
Mar
(68) |
Apr
(20) |
May
(34) |
Jun
(39) |
Jul
(23) |
Aug
(9) |
Sep
(32) |
Oct
(11) |
Nov
(8) |
Dec
(13) |
| 2009 |
Jan
(13) |
Feb
(20) |
Mar
(6) |
Apr
(8) |
May
(20) |
Jun
(5) |
Jul
(3) |
Aug
|
Sep
(1) |
Oct
(2) |
Nov
(3) |
Dec
(12) |
| 2010 |
Jan
(3) |
Feb
(10) |
Mar
(3) |
Apr
(3) |
May
(3) |
Jun
(1) |
Jul
(7) |
Aug
(4) |
Sep
(2) |
Oct
(12) |
Nov
(23) |
Dec
(25) |
| 2011 |
Jan
(4) |
Feb
(30) |
Mar
(16) |
Apr
(9) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Dan P. <dan...@gm...> - 2011-02-14 10:25:59
|
Dear Chris, waiting several days before announcing the final version, and doing more testing on more platforms is a sound approach. Sounds really good to me. One never knows where more bugs lurk. Best regards, Dan On Sun, Feb 13, 2011 at 11:31 PM, Dimitry Polivaev <dpo...@gm...> wrote: > Congratulations and best wishes! > > Dimitry. > >> Dear Dan, >> >> the final version is published at the file section. >> >> I'll wait some few days, before doing the announcement. >> Before, I'll test the versions on all platforms for being functional. >> >> Best regards, >> >> Chris |
|
From: Dan P. <dan...@gm...> - 2011-02-14 10:21:13
|
Hello Chris, I really see no need to move the wiki to a hosted app. We can restrict the editing to admins, as Dimitry mentioned, if you see the spam as such a big problem. Recently, I have been extending the spam filter with further filtering terms, and it seems to work in part, but requires more finetuning with more anti-spam terms. Admittedly, we do not get much useful contribution to wiki by non-admins anyway, so locking it down to admins seems a workable idea. Best regards, Dan On Sun, Feb 13, 2011 at 11:49 PM, Dimitry Polivaev <dpo...@gm...> wrote: >> I'm still very disappointed of the contents of this wiki especially all >> that spam. > > In Freeplane only wiki admins are allowed to edit wiki pages. If someone wants to edit the wiki he > writes in our forum his wiki user name to be allowed to do it. Such people so not became > bureaucrats, they can not change other people's roles, they can only edit. This way we have now spam > any more. > > Regards, > Dimitry > |
|
From: Dimitry P. <dpo...@gm...> - 2011-02-13 22:50:08
|
> I'm still very disappointed of the contents of this wiki especially all > that spam. In Freeplane only wiki admins are allowed to edit wiki pages. If someone wants to edit the wiki he writes in our forum his wiki user name to be allowed to do it. Such people so not became bureaucrats, they can not change other people's roles, they can only edit. This way we have now spam any more. Regards, Dimitry |
|
From: Dimitry P. <dpo...@gm...> - 2011-02-13 22:31:50
|
Congratulations and best wishes! Dimitry. > Dear Dan, > > the final version is published at the file section. > > I'll wait some few days, before doing the announcement. > Before, I'll test the versions on all platforms for being functional. > > Best regards, > > Chris |
|
From: Christian F. (GMX) <chr...@gm...> - 2011-02-13 17:35:27
|
Dear Dan, the final version is published at the file section. I'll wait some few days, before doing the announcement. Before, I'll test the versions on all platforms for being functional. Best regards, Chris |
|
From: Christian F. (GMX) <chr...@gm...> - 2011-02-13 17:17:32
|
Dear Dan, ok, seems done. The settings have been changed in the mediawiki versions. BTW: You can edit the file via sftp. https://sourceforge.net/apps/trac/sourceforge/wiki/Project%20web#ChangesasofFebruary2011 I'm still very disappointed of the contents of this wiki especially all that spam. I tried to move the wiki to a hosted app: https://sourceforge.net/apps/mediawiki/freemind/index.php?title=Main_Page Advantages: * almost no spam, due to user management by sf.net * Security fixes for mediawiki by sf.net Disadvantages/Problems: * How to integrate mindmaps (former <mm> extension, which can't be installed here). Any ideas? * Ads by google at the top.... Still to do: * Missing images Perhaps, you have some ideas. Best regards, Chris Am 13.02.11 14:54, schrieb Dan Polansky: > Hello Chris, > > sounds great! However, anons are now able to edit the wiki. There > should be a way to prevent this, by editing LocalSettings.php. > Preventing anonymous editing worked before the wiki upgrade, but for > some reasons no longer works. Maybe the new version of MediaWiki has a > different way of preventing anonymous editing; I don't know. I cannot > edit LocalSettings.php myself. > > Best regads, > Dan > > > On Sat, Feb 12, 2011 at 1:40 PM, Christian Foltin > <chr...@gm...> wrote: >> Dear all, >> >> currently, our web page is not available (ie. empty). >> The cause may be, that our old mediawiki version doesn't support php5.3. >> Thus, I'm upgrading to the latest mediawiki currently. >> >> Best regards, >> >> Chris > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Freemind-developer mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemind-developer > |
|
From: Dan P. <dan...@gm...> - 2011-02-13 13:54:45
|
Hello Chris, sounds great! However, anons are now able to edit the wiki. There should be a way to prevent this, by editing LocalSettings.php. Preventing anonymous editing worked before the wiki upgrade, but for some reasons no longer works. Maybe the new version of MediaWiki has a different way of preventing anonymous editing; I don't know. I cannot edit LocalSettings.php myself. Best regads, Dan On Sat, Feb 12, 2011 at 1:40 PM, Christian Foltin <chr...@gm...> wrote: > Dear all, > > currently, our web page is not available (ie. empty). > The cause may be, that our old mediawiki version doesn't support php5.3. > Thus, I'm upgrading to the latest mediawiki currently. > > Best regards, > > Chris |
|
From: Christian F. <chr...@gm...> - 2011-02-12 12:40:46
|
Dear all, currently, our web page is not available (ie. empty). The cause may be, that our old mediawiki version doesn't support php5.3. Thus, I'm upgrading to the latest mediawiki currently. Best regards, Chris -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de |
|
From: Dan P. <dan...@gm...> - 2011-02-07 07:53:32
|
Hello Chris, switching to git may be a good idea. Nonetheless, CVS problems of SourceForge seem to be a poor reason for the switch: SourceForge is likely to get CVS working again soon. I will need to update all the hyperlinks in the wiki that link to CVS; many development pages link to CVS for easy viewing of the related code. I can imagine some benefits of switching to git, given git is more modern than CVS and some SF projects have switched away from CVS (not always to git), but just please consider that there are also associated costs. Best regards, Dan On Sun, Feb 6, 2011 at 10:18 PM, Christian Foltin (GMX) <chr...@gm...> wrote: > Dear all, > > due to the CVS problems of sf I switched to git. > You can get the current code there: > > http://freemind.git.sourceforge.net/git/gitweb.cgi?p=freemind/freemind;a=shortlog;h=HEAD > > Best regards, > > Chris > > ------------------------------------------------------------------------------ > The modern datacenter depends on network connectivity to access resources > and provide services. The best practices for maximizing a physical server's > connectivity to a physical network are well understood - see how these > rules translate into the virtual world? > http://p.sf.net/sfu/oracle-sfdevnlfb > _______________________________________________ > Freemind-developer mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemind-developer > |
|
From: Christian F. (GMX) <chr...@gm...> - 2011-02-06 21:18:36
|
Dear all, due to the CVS problems of sf I switched to git. You can get the current code there: http://freemind.git.sourceforge.net/git/gitweb.cgi?p=freemind/freemind;a=shortlog;h=HEAD Best regards, Chris |
|
From: Dan P. <dan...@gm...> - 2011-01-30 17:40:58
|
Hello Chris, I have tested 0.9.0 RC15 and have found no errors that would block final release. All remaining bugs seem acceptable for final release, given how late the release already is. From the role of the unofficial quality manager of FreeMind, I am herewith giving go ahead to the final release of 0.9.0. You have rejected to fix some bugs or issues, for various reasons. Rejected bugs include "3. Long node editor not below node", "4. Option for plain text in notes", and "23. Drag and drop of two connected nodes drops arrow link". I would recommend that we watch for new critical bugs after the final release of 0.9.0, which is expected to be used by many more people than betas and RCs. If new critical bugs are discovered, there can be a bug-fix release 0.9.1. Thank you for all your effort in this marathon. Best regards, Dan |
|
From: Christian F. (GMX) <chr...@gm...> - 2011-01-25 21:03:51
|
Hi, 0.9.0 RC15 is published at sf. Best regards, Chris Am 11.01.11 19:40, schrieb Dan Polansky: > Hello Chris, > > I have just tested 0.9.0 RC15 from CVS against the bug 22; the test > showed that bug 22 is fixed. Thank you. > > Postponing fixing bug 23 to 0.9.1 is suboptimal but acceptable IMHO. > Given that you say that fixing the bug is too much work, given that > the bug is fairly easy to spot (hard to overlook) for the user, and > given how late 0.9.0 already is, it seems excusable to leave the bug > in the final release in spite of the bug being a data loss one. > > I know of no other serious bugs that block final release 0.9.0. I > would have one last thorough look at 0.9.0 RC15 after it is released > at SourceForge, and then I would give it a go ahead. > > Best regards, > Dan > > > On Sun, Jan 9, 2011 at 10:24 PM, Christian Foltin (GMX) > <chr...@gm...> wrote: >> Dear Dan, >> >> bug 22 is fixed in CVS. Bug 23 is not going to be fixed immediately as >> this involves lot of work. >> It is definitively left for 0.9.1. >> >> Best regards, >> >> Chris. >> >> PS: Do you get the CVS version on your own? >> >> >> Am 27.12.10 20:22, schrieb Dan Polansky: >>> Hello Chris, >>> >>> the ultimate decision is up to you, as you are the project director. >>> Whatever I decide or propose, you can override it. Nonetheless, within >>> the constrained and subordinate role of the unofficial quality manager >>> of FreeMind, I feel uncomfortable giving go ahead to a version that >>> contains known bugs that lead to data loss. >>> >>> Both bugs 22 and 23 are related to data loss. Especially bug 22 is >>> rather insidious, easy to be overlooked by the affected user. Bug 23 >>> is rather unlikely to be overlooked by the user, so it could really be >>> postponed for 0.9.1, but it is a data loss bug nonetheless. >>> >>> I am fully aware of the time pressure to release final FreeMind 0.9.0, >>> which is why I do not report here some regression bugs that are less >>> serious. From where I am standing, we seem to be really close to final >>> release. >>> >>> Best regards, >>> Dan >>> >>> >>> On Mon, Dec 27, 2010 at 5:53 PM, Christian Foltin (GMX) >>> <chr...@gm...> wrote: >>>> Hi Dan, >>>> >>>> sorry, if we continue like this, we'll never publish 0.9.0. >>>> >>>> IMHO, these bugs are not that dramatic. >>>> Let's postpone them. >>>> >>>> Best regards, Chris >>>> >>>> Am 27.12.10 10:33, schrieb Dan Polansky: >>>>> Hello Chris, >>>>> >>>>> I have found two more bugs related to data loss, by extending a test >>>>> mind map with even more cases in which something could go wrong in >>>>> conversion from 0.8.0 to 0.9.0. >>>>> >>>>> 22. Conversion from 0.8.0 to 0.9.0 drops encrypted arrow links >>>>> http://sourceforge.net/tracker/?func=detail&aid=3145871&group_id=7118&atid=107118 >>>>> >>>>> 23. Drag and drop of two connected nodes drops arrow link >>>>> http://sourceforge.net/tracker/?func=detail&aid=3145900&group_id=7118&atid=107118 >>>>> >>>>> I am sorry, again, that I did not discover these bug earlier. >>>>> Unfortunately, my brain seems to be much more eager to think about >>>>> what can go wrong when there are no more bugs on the list to be fixed. >>>>> >>>>> Best regards, >>>>> Dan > > ------------------------------------------------------------------------------ > Protect Your Site and Customers from Malware Attacks > Learn about various malware tactics and how to avoid them. Understand > malware threats, the impact they can have on your business, and how you > can protect your company and customers by using code signing. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Freemind-developer mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemind-developer |
|
From: Dan P. <dan...@gm...> - 2011-01-11 18:40:15
|
Hello Chris, I have just tested 0.9.0 RC15 from CVS against the bug 22; the test showed that bug 22 is fixed. Thank you. Postponing fixing bug 23 to 0.9.1 is suboptimal but acceptable IMHO. Given that you say that fixing the bug is too much work, given that the bug is fairly easy to spot (hard to overlook) for the user, and given how late 0.9.0 already is, it seems excusable to leave the bug in the final release in spite of the bug being a data loss one. I know of no other serious bugs that block final release 0.9.0. I would have one last thorough look at 0.9.0 RC15 after it is released at SourceForge, and then I would give it a go ahead. Best regards, Dan On Sun, Jan 9, 2011 at 10:24 PM, Christian Foltin (GMX) <chr...@gm...> wrote: > Dear Dan, > > bug 22 is fixed in CVS. Bug 23 is not going to be fixed immediately as > this involves lot of work. > It is definitively left for 0.9.1. > > Best regards, > > Chris. > > PS: Do you get the CVS version on your own? > > > Am 27.12.10 20:22, schrieb Dan Polansky: >> Hello Chris, >> >> the ultimate decision is up to you, as you are the project director. >> Whatever I decide or propose, you can override it. Nonetheless, within >> the constrained and subordinate role of the unofficial quality manager >> of FreeMind, I feel uncomfortable giving go ahead to a version that >> contains known bugs that lead to data loss. >> >> Both bugs 22 and 23 are related to data loss. Especially bug 22 is >> rather insidious, easy to be overlooked by the affected user. Bug 23 >> is rather unlikely to be overlooked by the user, so it could really be >> postponed for 0.9.1, but it is a data loss bug nonetheless. >> >> I am fully aware of the time pressure to release final FreeMind 0.9.0, >> which is why I do not report here some regression bugs that are less >> serious. From where I am standing, we seem to be really close to final >> release. >> >> Best regards, >> Dan >> >> >> On Mon, Dec 27, 2010 at 5:53 PM, Christian Foltin (GMX) >> <chr...@gm...> wrote: >>> Hi Dan, >>> >>> sorry, if we continue like this, we'll never publish 0.9.0. >>> >>> IMHO, these bugs are not that dramatic. >>> Let's postpone them. >>> >>> Best regards, Chris >>> >>> Am 27.12.10 10:33, schrieb Dan Polansky: >>>> Hello Chris, >>>> >>>> I have found two more bugs related to data loss, by extending a test >>>> mind map with even more cases in which something could go wrong in >>>> conversion from 0.8.0 to 0.9.0. >>>> >>>> 22. Conversion from 0.8.0 to 0.9.0 drops encrypted arrow links >>>> http://sourceforge.net/tracker/?func=detail&aid=3145871&group_id=7118&atid=107118 >>>> >>>> 23. Drag and drop of two connected nodes drops arrow link >>>> http://sourceforge.net/tracker/?func=detail&aid=3145900&group_id=7118&atid=107118 >>>> >>>> I am sorry, again, that I did not discover these bug earlier. >>>> Unfortunately, my brain seems to be much more eager to think about >>>> what can go wrong when there are no more bugs on the list to be fixed. >>>> >>>> Best regards, >>>> Dan |
|
From: Christian F. (GMX) <chr...@gm...> - 2011-01-09 21:24:28
|
Dear Dan, bug 22 is fixed in CVS. Bug 23 is not going to be fixed immediately as this involves lot of work. It is definitively left for 0.9.1. Best regards, Chris. PS: Do you get the CVS version on your own? Am 27.12.10 20:22, schrieb Dan Polansky: > Hello Chris, > > the ultimate decision is up to you, as you are the project director. > Whatever I decide or propose, you can override it. Nonetheless, within > the constrained and subordinate role of the unofficial quality manager > of FreeMind, I feel uncomfortable giving go ahead to a version that > contains known bugs that lead to data loss. > > Both bugs 22 and 23 are related to data loss. Especially bug 22 is > rather insidious, easy to be overlooked by the affected user. Bug 23 > is rather unlikely to be overlooked by the user, so it could really be > postponed for 0.9.1, but it is a data loss bug nonetheless. > > I am fully aware of the time pressure to release final FreeMind 0.9.0, > which is why I do not report here some regression bugs that are less > serious. From where I am standing, we seem to be really close to final > release. > > Best regards, > Dan > > > On Mon, Dec 27, 2010 at 5:53 PM, Christian Foltin (GMX) > <chr...@gm...> wrote: >> Hi Dan, >> >> sorry, if we continue like this, we'll never publish 0.9.0. >> >> IMHO, these bugs are not that dramatic. >> Let's postpone them. >> >> Best regards, Chris >> >> Am 27.12.10 10:33, schrieb Dan Polansky: >>> Hello Chris, >>> >>> I have found two more bugs related to data loss, by extending a test >>> mind map with even more cases in which something could go wrong in >>> conversion from 0.8.0 to 0.9.0. >>> >>> 22. Conversion from 0.8.0 to 0.9.0 drops encrypted arrow links >>> http://sourceforge.net/tracker/?func=detail&aid=3145871&group_id=7118&atid=107118 >>> >>> 23. Drag and drop of two connected nodes drops arrow link >>> http://sourceforge.net/tracker/?func=detail&aid=3145900&group_id=7118&atid=107118 >>> >>> I am sorry, again, that I did not discover these bug earlier. >>> Unfortunately, my brain seems to be much more eager to think about >>> what can go wrong when there are no more bugs on the list to be fixed. >>> >>> Best regards, >>> Dan > > ------------------------------------------------------------------------------ > Learn how Oracle Real Application Clusters (RAC) One Node allows customers > to consolidate database storage, standardize their database environment, and, > should the need arise, upgrade to a full multi-node Oracle RAC database > without downtime or disruption > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Freemind-developer mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemind-developer |
|
From: Dan P. <dan...@gm...> - 2010-12-27 19:22:44
|
Hello Chris, the ultimate decision is up to you, as you are the project director. Whatever I decide or propose, you can override it. Nonetheless, within the constrained and subordinate role of the unofficial quality manager of FreeMind, I feel uncomfortable giving go ahead to a version that contains known bugs that lead to data loss. Both bugs 22 and 23 are related to data loss. Especially bug 22 is rather insidious, easy to be overlooked by the affected user. Bug 23 is rather unlikely to be overlooked by the user, so it could really be postponed for 0.9.1, but it is a data loss bug nonetheless. I am fully aware of the time pressure to release final FreeMind 0.9.0, which is why I do not report here some regression bugs that are less serious. From where I am standing, we seem to be really close to final release. Best regards, Dan On Mon, Dec 27, 2010 at 5:53 PM, Christian Foltin (GMX) <chr...@gm...> wrote: > Hi Dan, > > sorry, if we continue like this, we'll never publish 0.9.0. > > IMHO, these bugs are not that dramatic. > Let's postpone them. > > Best regards, Chris > > Am 27.12.10 10:33, schrieb Dan Polansky: >> Hello Chris, >> >> I have found two more bugs related to data loss, by extending a test >> mind map with even more cases in which something could go wrong in >> conversion from 0.8.0 to 0.9.0. >> >> 22. Conversion from 0.8.0 to 0.9.0 drops encrypted arrow links >> http://sourceforge.net/tracker/?func=detail&aid=3145871&group_id=7118&atid=107118 >> >> 23. Drag and drop of two connected nodes drops arrow link >> http://sourceforge.net/tracker/?func=detail&aid=3145900&group_id=7118&atid=107118 >> >> I am sorry, again, that I did not discover these bug earlier. >> Unfortunately, my brain seems to be much more eager to think about >> what can go wrong when there are no more bugs on the list to be fixed. >> >> Best regards, >> Dan |
|
From: Christian F. (GMX) <chr...@gm...> - 2010-12-27 16:53:33
|
Hi Dan, sorry, if we continue like this, we'll never publish 0.9.0. IMHO, these bugs are not that dramatic. Let's postpone them. Best regards, Chris Am 27.12.10 10:33, schrieb Dan Polansky: > Hello Chris, > > I have found two more bugs related to data loss, by extending a test > mind map with even more cases in which something could go wrong in > conversion from 0.8.0 to 0.9.0. > > 22. Conversion from 0.8.0 to 0.9.0 drops encrypted arrow links > http://sourceforge.net/tracker/?func=detail&aid=3145871&group_id=7118&atid=107118 > > 23. Drag and drop of two connected nodes drops arrow link > http://sourceforge.net/tracker/?func=detail&aid=3145900&group_id=7118&atid=107118 > > I am sorry, again, that I did not discover these bug earlier. > Unfortunately, my brain seems to be much more eager to think about > what can go wrong when there are no more bugs on the list to be fixed. > > Best regards, > Dan > > ------------------------------------------------------------------------------ > Learn how Oracle Real Application Clusters (RAC) One Node allows customers > to consolidate database storage, standardize their database environment, and, > should the need arise, upgrade to a full multi-node Oracle RAC database > without downtime or disruption > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Freemind-developer mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemind-developer > |
|
From: Dan P. <dan...@gm...> - 2010-12-27 09:33:17
|
Hello Chris, I have found two more bugs related to data loss, by extending a test mind map with even more cases in which something could go wrong in conversion from 0.8.0 to 0.9.0. 22. Conversion from 0.8.0 to 0.9.0 drops encrypted arrow links http://sourceforge.net/tracker/?func=detail&aid=3145871&group_id=7118&atid=107118 23. Drag and drop of two connected nodes drops arrow link http://sourceforge.net/tracker/?func=detail&aid=3145900&group_id=7118&atid=107118 I am sorry, again, that I did not discover these bug earlier. Unfortunately, my brain seems to be much more eager to think about what can go wrong when there are no more bugs on the list to be fixed. Best regards, Dan |
|
From: Dan P. <dan...@gm...> - 2010-12-24 09:47:45
|
Hello Chris, thank you for the rapid bug fix! I have tested 0.9.0 RC14 against all the mind maps that I use to test the conversion from 0.8.1 to 0.9.0, and everything looks good, ready for the final release. Nonetheless, please give me some more time to once more thoroughly test 0.9.0 RC14; this test that I have made has been hasty and without my full attention, performed under time pressure. Merry Christmas! Best regards, Dan On Fri, Dec 24, 2010 at 12:08 AM, Christian Foltin (GMX) <chr...@gm...> wrote: > Dear Dan, > > we've encountered a long known java bug: > > http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4508058 > > I've fixed it the usual way and, currently, RC14 is publishing on SF. > (By the way, now some other (UTF) encodings should be supported, too.) > > HTH, Chris > > PS: Mery christmas! > > Am 22.12.10 20:21, schrieb Dan Polansky: >> Hello Chris, >> >> unfortunately, I have discovered a conversion bug that was already >> fixed in 0.9.0 RC5 and reappeared in 0.9.0 RC11, and persist in 0.9.0 >> RC13 (the bug is not there in 0.9.0 RC10). I am sorry I did not >> discover the bug earlier; possibly, I have failed to notice the >> problem because of the too quiet failure on conversion to 0.9.0 that >> was introduced in 0.9.0 RC11 and removed in 0.9.0 RC13. >> >> 21. Byte-order mark for UTF-8 (BOM) produces failure to load >> http://sourceforge.net/tracker/?func=detail&aid=3141875&group_id=7118&atid=107118 >> >> Best regards, >> Dan >> >> >> On Sun, Dec 19, 2010 at 10:09 PM, Christian Foltin (GMX) >> <chr...@gm...> wrote: >>> Hi Dan, >>> >>> done, although ... >>> >>> Best regards, Chris >>> >>> Am 18.12.10 07:54, schrieb Dan Polansky: >>>> Hello Chris, >>>> >>>> thank you for your removing align=left. >>>> >>>> From the point of view of a clean process, there should IMHO better be >>>> a version 0.9.0 RC13. Then I can close the bugs in the bug tracker >>>> against this version, and after a week or so after the release of >>>> 0.9.0 RC13, a final version can be released that is identical to 0.9.0 >>>> RC13. >>>> >>>> My understanding of a good process of final release is that the the >>>> final release should be identical to the last published RC version. As >>>> our recent experience shows, an RC version sometimes contains bugs >>>> that were thought to be fixed in the RC version, or contains new bugs >>>> or issues. I do not really think that there are going to be any >>>> problems with RC13, but my estimation can turn wrong, hence it would >>>> be better to keep this process, I think. >>>> >>>> Best regards, >>>> Dan >>>> >>> >>> ------------------------------------------------------------------------------ >>> Lotusphere 2011 >>> Register now for Lotusphere 2011 and learn how >>> to connect the dots, take your collaborative environment >>> to the next level, and enter the era of Social Business. >>> http://p.sf.net/sfu/lotusphere-d2d >>> _______________________________________________ >>> Freemind-developer mailing list >>> Fre...@li... >>> https://lists.sourceforge.net/lists/listinfo/freemind-developer >>> >> >> ------------------------------------------------------------------------------ >> Learn how Oracle Real Application Clusters (RAC) One Node allows customers >> to consolidate database storage, standardize their database environment, and, >> should the need arise, upgrade to a full multi-node Oracle RAC database >> without downtime or disruption >> http://p.sf.net/sfu/oracle-sfdevnl >> _______________________________________________ >> Freemind-developer mailing list >> Fre...@li... >> https://lists.sourceforge.net/lists/listinfo/freemind-developer > > ------------------------------------------------------------------------------ > Learn how Oracle Real Application Clusters (RAC) One Node allows customers > to consolidate database storage, standardize their database environment, and, > should the need arise, upgrade to a full multi-node Oracle RAC database > without downtime or disruption > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Freemind-developer mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemind-developer > |
|
From: Christian F. (GMX) <chr...@gm...> - 2010-12-23 23:08:59
|
Dear Dan, we've encountered a long known java bug: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4508058 I've fixed it the usual way and, currently, RC14 is publishing on SF. (By the way, now some other (UTF) encodings should be supported, too.) HTH, Chris PS: Mery christmas! Am 22.12.10 20:21, schrieb Dan Polansky: > Hello Chris, > > unfortunately, I have discovered a conversion bug that was already > fixed in 0.9.0 RC5 and reappeared in 0.9.0 RC11, and persist in 0.9.0 > RC13 (the bug is not there in 0.9.0 RC10). I am sorry I did not > discover the bug earlier; possibly, I have failed to notice the > problem because of the too quiet failure on conversion to 0.9.0 that > was introduced in 0.9.0 RC11 and removed in 0.9.0 RC13. > > 21. Byte-order mark for UTF-8 (BOM) produces failure to load > http://sourceforge.net/tracker/?func=detail&aid=3141875&group_id=7118&atid=107118 > > Best regards, > Dan > > > On Sun, Dec 19, 2010 at 10:09 PM, Christian Foltin (GMX) > <chr...@gm...> wrote: >> Hi Dan, >> >> done, although ... >> >> Best regards, Chris >> >> Am 18.12.10 07:54, schrieb Dan Polansky: >>> Hello Chris, >>> >>> thank you for your removing align=left. >>> >>> From the point of view of a clean process, there should IMHO better be >>> a version 0.9.0 RC13. Then I can close the bugs in the bug tracker >>> against this version, and after a week or so after the release of >>> 0.9.0 RC13, a final version can be released that is identical to 0.9.0 >>> RC13. >>> >>> My understanding of a good process of final release is that the the >>> final release should be identical to the last published RC version. As >>> our recent experience shows, an RC version sometimes contains bugs >>> that were thought to be fixed in the RC version, or contains new bugs >>> or issues. I do not really think that there are going to be any >>> problems with RC13, but my estimation can turn wrong, hence it would >>> be better to keep this process, I think. >>> >>> Best regards, >>> Dan >>> >> >> ------------------------------------------------------------------------------ >> Lotusphere 2011 >> Register now for Lotusphere 2011 and learn how >> to connect the dots, take your collaborative environment >> to the next level, and enter the era of Social Business. >> http://p.sf.net/sfu/lotusphere-d2d >> _______________________________________________ >> Freemind-developer mailing list >> Fre...@li... >> https://lists.sourceforge.net/lists/listinfo/freemind-developer >> > > ------------------------------------------------------------------------------ > Learn how Oracle Real Application Clusters (RAC) One Node allows customers > to consolidate database storage, standardize their database environment, and, > should the need arise, upgrade to a full multi-node Oracle RAC database > without downtime or disruption > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Freemind-developer mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemind-developer |
|
From: Dan P. <dan...@gm...> - 2010-12-22 19:27:42
|
An afterthought: my error: I have failed to notice the problem because I have failed to test Cars.mm in the first place. When I open Cars.mm in 0.9.0 RC11, the failure is conspicuous. I have no clue why I have omitted Cars.mm from the test. --Dan On Wed, Dec 22, 2010 at 8:21 PM, Dan Polansky <dan...@gm...> wrote: > Hello Chris, > > unfortunately, I have discovered a conversion bug that was already > fixed in 0.9.0 RC5 and reappeared in 0.9.0 RC11, and persist in 0.9.0 > RC13 (the bug is not there in 0.9.0 RC10). I am sorry I did not > discover the bug earlier; possibly, I have failed to notice the > problem because of the too quiet failure on conversion to 0.9.0 that > was introduced in 0.9.0 RC11 and removed in 0.9.0 RC13. > > 21. Byte-order mark for UTF-8 (BOM) produces failure to load > http://sourceforge.net/tracker/?func=detail&aid=3141875&group_id=7118&atid=107118 > > Best regards, > Dan > > > On Sun, Dec 19, 2010 at 10:09 PM, Christian Foltin (GMX) > <chr...@gm...> wrote: >> Hi Dan, >> >> done, although ... >> >> Best regards, Chris >> >> Am 18.12.10 07:54, schrieb Dan Polansky: >>> Hello Chris, >>> >>> thank you for your removing align=left. >>> >>> From the point of view of a clean process, there should IMHO better be >>> a version 0.9.0 RC13. Then I can close the bugs in the bug tracker >>> against this version, and after a week or so after the release of >>> 0.9.0 RC13, a final version can be released that is identical to 0.9.0 >>> RC13. >>> >>> My understanding of a good process of final release is that the the >>> final release should be identical to the last published RC version. As >>> our recent experience shows, an RC version sometimes contains bugs >>> that were thought to be fixed in the RC version, or contains new bugs >>> or issues. I do not really think that there are going to be any >>> problems with RC13, but my estimation can turn wrong, hence it would >>> be better to keep this process, I think. >>> >>> Best regards, >>> Dan >>> >> >> ------------------------------------------------------------------------------ >> Lotusphere 2011 >> Register now for Lotusphere 2011 and learn how >> to connect the dots, take your collaborative environment >> to the next level, and enter the era of Social Business. >> http://p.sf.net/sfu/lotusphere-d2d >> _______________________________________________ >> Freemind-developer mailing list >> Fre...@li... >> https://lists.sourceforge.net/lists/listinfo/freemind-developer >> > |
|
From: Dan P. <dan...@gm...> - 2010-12-22 19:21:36
|
Hello Chris, unfortunately, I have discovered a conversion bug that was already fixed in 0.9.0 RC5 and reappeared in 0.9.0 RC11, and persist in 0.9.0 RC13 (the bug is not there in 0.9.0 RC10). I am sorry I did not discover the bug earlier; possibly, I have failed to notice the problem because of the too quiet failure on conversion to 0.9.0 that was introduced in 0.9.0 RC11 and removed in 0.9.0 RC13. 21. Byte-order mark for UTF-8 (BOM) produces failure to load http://sourceforge.net/tracker/?func=detail&aid=3141875&group_id=7118&atid=107118 Best regards, Dan On Sun, Dec 19, 2010 at 10:09 PM, Christian Foltin (GMX) <chr...@gm...> wrote: > Hi Dan, > > done, although ... > > Best regards, Chris > > Am 18.12.10 07:54, schrieb Dan Polansky: >> Hello Chris, >> >> thank you for your removing align=left. >> >> From the point of view of a clean process, there should IMHO better be >> a version 0.9.0 RC13. Then I can close the bugs in the bug tracker >> against this version, and after a week or so after the release of >> 0.9.0 RC13, a final version can be released that is identical to 0.9.0 >> RC13. >> >> My understanding of a good process of final release is that the the >> final release should be identical to the last published RC version. As >> our recent experience shows, an RC version sometimes contains bugs >> that were thought to be fixed in the RC version, or contains new bugs >> or issues. I do not really think that there are going to be any >> problems with RC13, but my estimation can turn wrong, hence it would >> be better to keep this process, I think. >> >> Best regards, >> Dan >> > > ------------------------------------------------------------------------------ > Lotusphere 2011 > Register now for Lotusphere 2011 and learn how > to connect the dots, take your collaborative environment > to the next level, and enter the era of Social Business. > http://p.sf.net/sfu/lotusphere-d2d > _______________________________________________ > Freemind-developer mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemind-developer > |
|
From: Christian F. (GMX) <chr...@gm...> - 2010-12-19 21:09:23
|
Hi Dan, done, although ... Best regards, Chris Am 18.12.10 07:54, schrieb Dan Polansky: > Hello Chris, > > thank you for your removing align=left. > > From the point of view of a clean process, there should IMHO better be > a version 0.9.0 RC13. Then I can close the bugs in the bug tracker > against this version, and after a week or so after the release of > 0.9.0 RC13, a final version can be released that is identical to 0.9.0 > RC13. > > My understanding of a good process of final release is that the the > final release should be identical to the last published RC version. As > our recent experience shows, an RC version sometimes contains bugs > that were thought to be fixed in the RC version, or contains new bugs > or issues. I do not really think that there are going to be any > problems with RC13, but my estimation can turn wrong, hence it would > be better to keep this process, I think. > > Best regards, > Dan > |
|
From: Dan P. <dan...@gm...> - 2010-12-18 06:54:28
|
Hello Chris,
thank you for your removing align=left.
>From the point of view of a clean process, there should IMHO better be
a version 0.9.0 RC13. Then I can close the bugs in the bug tracker
against this version, and after a week or so after the release of
0.9.0 RC13, a final version can be released that is identical to 0.9.0
RC13.
My understanding of a good process of final release is that the the
final release should be identical to the last published RC version. As
our recent experience shows, an RC version sometimes contains bugs
that were thought to be fixed in the RC version, or contains new bugs
or issues. I do not really think that there are going to be any
problems with RC13, but my estimation can turn wrong, hence it would
be better to keep this process, I think.
Best regards,
Dan
On Fri, Dec 17, 2010 at 9:51 PM, Christian Foltin (GMX)
<chr...@gm...> wrote:
> Hi Dan,
>
> to end up this discussion, I've removed the align=left in the CVS
> version of the updater script.
>
> I you don't mind, I'm going to release the 0.9.0 version.
> Do you have any important objections?
>
> Best regards,
>
> Chris
>
> Am 10.12.10 19:55, schrieb Dan Polansky:
>> Hello Chris,
>>
>> I have tested your changes by updating my version of FreeMind 0.9.0 in
>> Eclipse from CVS, and running FreeMind from Eclipse.
>>
>> Re removing of the "Xalan" string: works fine.
>>
>> Re conspicous failure: it works. I have tested the thing by placing
>> "throw new Exception("Artificial exception");" before the line
>> "successful = true" in the class "TransformerRunnable" in Tools.java.
>>
>> Re '<p align="left">': I do not understand your explanation. There is
>> no '<p align="left">' in the HTML source of rich text long nodes, so I
>> do not see why there should be '<p align="left">' in the HTML source
>> of notes. When you create a long plain text node, then switch it to
>> rich text, and then look at the HTML source, there is no
>> 'align="left"'; and that is how it should be, if you ask me. I do not
>> see any useful function that 'align="left"' serves, nor do I see any
>> technical necessity for it being there. I have looked at HTML
>> paragraph tags generated by MediaWiki, and they are plain ones, having
>> no 'align="left"'. So no matter how I think about it, I do not
>> understand the need.
>>
>> Best regards,
>> Dan
|
|
From: Christian F. (GMX) <chr...@gm...> - 2010-12-17 20:51:48
|
Hi Dan,
to end up this discussion, I've removed the align=left in the CVS
version of the updater script.
I you don't mind, I'm going to release the 0.9.0 version.
Do you have any important objections?
Best regards,
Chris
Am 10.12.10 19:55, schrieb Dan Polansky:
> Hello Chris,
>
> I have tested your changes by updating my version of FreeMind 0.9.0 in
> Eclipse from CVS, and running FreeMind from Eclipse.
>
> Re removing of the "Xalan" string: works fine.
>
> Re conspicous failure: it works. I have tested the thing by placing
> "throw new Exception("Artificial exception");" before the line
> "successful = true" in the class "TransformerRunnable" in Tools.java.
>
> Re '<p align="left">': I do not understand your explanation. There is
> no '<p align="left">' in the HTML source of rich text long nodes, so I
> do not see why there should be '<p align="left">' in the HTML source
> of notes. When you create a long plain text node, then switch it to
> rich text, and then look at the HTML source, there is no
> 'align="left"'; and that is how it should be, if you ask me. I do not
> see any useful function that 'align="left"' serves, nor do I see any
> technical necessity for it being there. I have looked at HTML
> paragraph tags generated by MediaWiki, and they are plain ones, having
> no 'align="left"'. So no matter how I think about it, I do not
> understand the need.
>
> Best regards,
> Dan
>
> ------------------------------------------------------------------------------
> Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
> new data types, scalar functions, improved concurrency, built-in packages,
> OCI, SQL*Plus, data movement tools, best practices and more.
> http://p.sf.net/sfu/oracle-sfdev2dev
> _______________________________________________
> Freemind-developer mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freemind-developer
>
|
|
From: Dan P. <dan...@gm...> - 2010-12-10 18:55:12
|
Hello Chris,
I have tested your changes by updating my version of FreeMind 0.9.0 in
Eclipse from CVS, and running FreeMind from Eclipse.
Re removing of the "Xalan" string: works fine.
Re conspicous failure: it works. I have tested the thing by placing
"throw new Exception("Artificial exception");" before the line
"successful = true" in the class "TransformerRunnable" in Tools.java.
Re '<p align="left">': I do not understand your explanation. There is
no '<p align="left">' in the HTML source of rich text long nodes, so I
do not see why there should be '<p align="left">' in the HTML source
of notes. When you create a long plain text node, then switch it to
rich text, and then look at the HTML source, there is no
'align="left"'; and that is how it should be, if you ask me. I do not
see any useful function that 'align="left"' serves, nor do I see any
technical necessity for it being there. I have looked at HTML
paragraph tags generated by MediaWiki, and they are plain ones, having
no 'align="left"'. So no matter how I think about it, I do not
understand the need.
Best regards,
Dan
|
