What's New tab for Loader

It's also beneficial to maintain a list of bugs that haven't yet been resolved, as is done on many of the SourceForge pages. Yes, I appreciate that all this takes time, but on the other hand issues raised in the forum can be resolved faster by referring the poster to a particular bug ID.

This is how I do it and I've no plans to do it otherwise.

Quote:

This is how I do it and I've no plans to do it otherwise.

Fine for sims. May we have the same for the Loader please?

Hmm, we've come a long way since this thread was opened. I guessed that those in the know use an issue tracker, since bug IDs occasionally surface. Well, the only solution I can think of is for rank and file members to keep their own searchable databases using programs such as Evernote to keep track of issues relating to our favourite sims and to ask whether a bug ID has been raised for anything that seems important.

As far as minor version releases, a brief thread from Geoff, Peter or Clive would certainly help even if only to say "minor bugs addressed" Additionally, the date of such a thread would help us determine whether strange behaviour antedates the update release or not.

I'm sure it wouldn't take any longer to create a new thread to this effect than it would for me to pull out my credit card and pay for another sim.

Quote:

This is how I do it and I've no plans to do it otherwise.

Fine for sims. May we have the same for the Loader please?

[quote] A version history / change log for the Loader was supposed to happen but I forgot. Simple as that

" said:

Hmm, we've come a long way since this thread was opened. I guessed that those in the know use an issue tracker, since bug IDs occasionally surface. Well, the only solution I can think of is for rank and file members to keep their own searchable databases using programs such as Evernote to keep track of issues relating to our favourite sims and to ask whether a bug ID has been raised for anything that seems important.

For the core code, there's stuff in the tracker ("Mantis"that doesn't want to be exposed because it will reveal stuff that isn't ready to be revealed. Geoff and I also use it for noting potential improvements that might not happen for a long time - or even at all - and that we wouldn't want exposed for that reason. So I'm not sure there's a practical way of publishing this stuff. Even having one of us work through the current list to produce a public list isn't practical - there are 353 issues with the core code open at the moment.

What I will say is that I'll try to remember to include Mantis numbers in future when I say something has been reported, and I ask other devs to do the same.

Quote:

As far as minor version releases, a brief thread from Geoff, Peter or Clive would certainly help even if only to say "minor bugs addressed" Additionally, the date of such a thread would help us determine whether strange behaviour antedates the update release or not.

I'm sure it wouldn't take any longer to create a new thread to this effect than it would for me to pull out my credit card and pay for another sim.

Geoff said above that he intends this for each release; it just got forgotten.

" said:

Quote:

This is how I do it and I've no plans to do it otherwise.

Fine for sims. May we have the same for the Loader please?

From Geoff's post earlier in the thread:

" said:

Quote:

A version history / change log for the Loader was supposed to happen but I forgot. Simple as that

there are 353 issues with the core code open at the moment.

this is only a idea but the stuff you do not want us to know about can you just blank it out and the stuff you do not mide use seeing can be left in

this is only a idea but the stuff you do not want us to know about can you just blank it out and the stuff you do not mide use seeing can be left in

" said:

there are 353 issues with the core code open at the moment.

That number includes feature requests.