A combination of both could also be quite user-friendly: Update the original release-posting with all the extra features and options you have (you have it summed up in a readme, right?) *and* make a new post with just the stuff added this time.
The reason I thought the last post was because when you hit the Last Post icon, that's where you go. Whereas, if you modify your release post, people would still need to jump to the last post and then back to the release post.
I'm sure there's a compromise/rational solution in here somewhere, just not sure what it is. Maybe like skwire has done it with his Launching Pad
except instead of a forum per coder, just a general forum where anyone who has written a program can start a thread with his/her own Launch Pad and can update it which would trigger it into being a New Post but users would reply back at the original thread.
(you have it summed up in a readme, right?)
Sorry, being a typical male I'm instruction-agnostic - just ask my other half
What's the logic in not doing this if someone else was the last poster?
Because alternating posts read more like a conversation.Current method for with OP replying to himself.OP:
I've release project X v0.1, see if there's any bugs.
(Couple of days later with no reply)OP:
Update X v0.02, fixed yaddayadda.
(Still no comment a few days later)OP:
WTF, it just nuked my drive! Don't use it!
That reads like a monologue, no indication of anyone taking any interest.What I suggest.OP:
Release project X v0.01, have fun. (Modified a couple of days later after no posts and promoted to New Post status)
Release v0.02, fixed drive nuking bit. Surprised no one caught it.New poster:
Hey thanks for that, you saved all my backed up GMail. (Maybe a month later)
That reads more like a conversation, interaction between users.
I don't know about you but if there is a string of consecutive posts from the same person, I tend to read the first and then jump to the next person unless there's something interesting referenced back to one of the first persons' other posts. (Read it slowly, it does make sense......kind of.)
this is what i do, i update the first post and change the subject to signify the current release version number and date, and then make a reply post with the changelog for the latest release.
Crap, I just noticed you could change the subject - still it's not something I like doing unless I'm the one who started the thread.
Remember I was talking about this more for the Coding Snacks area where the threads are started by others.