INTERACT FORUM
More => Old Versions => Media Center 11 (Development Ended) => Topic started by: Phydeaux on February 25, 2003, 06:32:18 am
-
Hello guys,
Someone mentioned this a little while ago, but I can't find the thread:
Is it possible to compile a history list of all bug fixes etc. and post it to a page, either in this forum, or on another page?
My reasoning is this: I don't have an internet connection at home (I live in Africa, and I'm a student -- pity me if you will) and I can only get updates when time permits and test them for bugs later.
Usually, by the time I get back to post my findings, you are a build (or FIVE, I remember once) ahead. Regulars will have noticed my build-behind-bug-posts for quite some time now.
Five builds ahead is great and it's not about that which I am complaining. It's just a pain to sift through all the other release threads and work out what's been changed, and whether I should bother looking and checking to see whether other bugs are updated or not.
It will provide a handy central resource for your beta-testers and while it might cost you a minute of your time to cut and paste it into a log file, it will save me several minutes of my (and other people's, I'm sure) time.
P.
-
Here:
ftp://ftp.jriver.com/pub/downloads/music/tmp/History.txt
It won't stay updated, but remind us and we can upload it again later.
-
My idea was to include a menu item within MJ that brought up a complete list of bug fixes from all of the version 9 builds. That list wouldn't be loaded from the internet, but from within MJ itself.
I would think that once the menu item was put in place, keeping it updated would be relatively simple. Just tack on the latest list of changes to the beginning and there you go.
Basically just include the text file, that Matt just posted a link to, with the build, and put a shortcut to it in the start menu folder would work too.
-
Sounds like a good idea to me.
A LOT of programs that undergo frequent builds have this - a list of all the bugs/features fixed/added per build.
It's pretty standard.
-
A bug tracking SYSTEM would be even better.
-
... bug tracking system ...
Please don't start that again. We like the way we work.
Adding new systems often means more time spent maintaining systems and less time writing code.
With respect to the history list suggestions, it's all there if you want to dig for it, and we're not going to change this anytime soon. I'd rather not have developers doing clerical work.
Everyone has a different sense of how these things should be done. In general, I'm happy with what we've got. I hope you can live with it.
-
I guess you would be then fixing bugs in the bug tracking system.
-
If the bug tracking system has too many bugs in it.
You might never actually get around to fixing the real bugs. Like the Library Inconsistent post for example
-
Listening to: 'That's Enough For Me' from 'Tusk' by 'Fleetwood Mac' on Media Center 9.0
Ripped by Hand from Vinyl to .ape
-
Jim,
How about this to do what you normally do and satisfy everyone:
Just start a thread called: Release History.
Every time a new build is released, post the fixes to this one thread as well as the build release thread. Make it sticky and lock it so that no one can post to it other than you, Matt etc.
This will give one thread that purely consists of version histories and isn't slowed down by tons of bug posts, suggestions etc. The only extra work it will require from your team is copying and pasteing to a second thread and it'll give an easy centralised history.
Would that be a feasible solution that wouldn't really waste any time?
-
Jim, I vote for Nila's suggestion. That should be dead simple, alloow you to keep a record, but at the same time take up 0.0001% of a developers time. C'mon Jim what do you say?
Graham
-
I would like to ask a question.
why are we talking about this.
I am sure that when something is reported, j river tryes it out if it is a bug it goes on a list (priorities are fixed first) when they get to it they get to it.
I don't see why everyone needs to get into there underware.
-
How about this to do what you normally do and satisfy everyone:
Just start a thread called: Release History. Every time a new build is released, post the fixes to this one thread as well as the build release thread.
Good idea, Nila. Be my guest. Open the thread and keep it up to date. Thanks for thinking of it.
-
I would like to ask a question.
why are we talking about this.
I am sure that when something is reported, j river tryes it out if it is a bug it goes on a list (priorities are fixed first) when they get to it they get to it.
I don't see why everyone needs to get into there underware.
Surely King, a bug list / fix / update log is a standard practise tool? I work for a Software Co (Not a developer I hasten to add), without Version Control . Bug lists / History / Fixes it would be difficult to operate!
PS I thought that the Interact boards were for all ideas / fixes / bug reprts / wishes / never never land?
Democracy rules etc?
Graham
-
Surely King, a bug list / fix / update log is a standard practise tool? I work for a Software Co (Not a developer I hasten to add), without Version Control . Bug lists / History / Fixes it would be difficult to operate!
Do you share it with your customers?
>> Democracy rules etc?
Not in a Dictatorship
-
Are you talking again King?
I thought I, as the current dictator, already spoke to you about that? ;D
-
Well I think I would be a good dictator
I had allot of practice in the military and was quite good at it.
-
Do you share it with your customers?
Of course not.
But I feel part of the family at J River!
-
But I feel part of the family at J River!
That's nice of you to say. Really.
-
That's nice of you to say. Really.
Wow Brother Jim, you working late too.
Fancy a glass?
-
You buying, mate?
Have to go for a jimmy.
-
You buying, mate?
Have to go for a jimmy.
Thers a nice ice cold glass of the black stuff (Guiness) waiting for you.
God knows i've had enough tonight.
At that I bid you good night - my beta testing is over for the day! I must go, water the horse, and feed my brain (with sleep)
OT - Am reading a brill book - may even start a new OT thread about it - Rich Dad, Poor dad by Robert Kiwalokolajkly (or something close - American/Japenese from Hawaii)
Iwill be a millionaire by Christmas (Italian Lira knowing my luck!)
graham
-
whats a jimmy, Beer?
-
Think after the beer....
It's Cockney Rhyming Slang.
The rules (I think) are these.
One word replaces another.
"Apples and pairs" rhymes with "stairs"
Apples in Cockney equals stairs in English.
I think.
Dog and Bone, Telephone
"Kin I use your dog, mate?"
Listening to: 'Marvin Gaye - 10 - Inner City Blues (Make Me Wanna Holler)' from 'Every Great Motown Hit of Marvin Gaye' by 'Marvin Gaye' on Media Center 9.0
-
Cockney Rhyming Slang started in the East End of London yonks ago. It's said that it was a way for crooks to talk to each other without being understood by outsiders. The basic principle is that the word to be rhymed is coupled with a phrase, not a single word, of which the last word of the phrase is rhymed. Then, only the first word of the phrase is used. For instance 'Apples and Pears', for stairs, becomes 'Apples'. ''Frog and Toad', for 'Road', becomes 'Frog'. 'Rub a Dub' for 'Pub', 'Vera Lynn' for 'Gin'.......thus giving
'I'm going down the apples and along the frog to the rub for a vera, etc etc.
Incidentally, Jimmy is 'Jimmy Riddle', an explanation of which is not necessary.
Keep ya' minces peeled!!!.....Jim
-
Here:
ftp://ftp.jriver.com/pub/downloads/music/tmp/History.txt
It won't stay updated, but remind us and we can upload it again later.