1.2.1 -> 1.2.2 Diffs

yes, of course i am aware now i should have kept a record of all my changes, but crowing after the fact is not all that helpful to me.
the draft issue is here (tracking that down has solved at least part of my problem). i write all my posts offline so when i enter a post, i want to publish it without messing with the post status settings every single time.

I can offer help on using the GNU diff tools in a POSIX environment.

i’m afraid since that sentence meant absolutely nothing to me diffs are going to be way beyond my expertise. i am going to look for the trackback patch now ??

Clicking the “publish” button doesn’t publish a post for you?

if that’s all you need to do to change the post status, why would there be a radio button for ‘publish’? i always assumed that for the post to publish the status would have to be ‘publish’ as well.

Re the original posts in this thread:
I’ve used WP for almost a year now, and have upgraded dozens of times when using nightly, alpha and beta builds. It used to take me ages to rebuild all the changes, esp before the advent of plugins, and I learnt two things the hard way:
1 – To keep a list, a written list, of all the files I had messed with.
2 – That the amount of ‘customising’ I did directly related to the amount of work I had done.
If you have invested time and energy in creating a site, then upgrading deserves as much diligence.
As for diffs.. what if through an oversight one diff was not included ? And that due to that something happened to your site ? You’d be coming back here not very happy I guess – but I really would not see that as the fault of either the devs or anyone else involved in preparing the code. If it’s code that will operate on your site, then you have to accept that and any risks. That applies whether its WordPress or any other server side code.
If you can generate diffs – do so.
If you cannot generate diffs – follow a full upgrade procedure
If you insist on only ever using files that you see have been changed, then – and no doubt someone will call me on this – you are increasing your chance of hitting an error. An error which could have been avoided by you.
And if anyone thinks that the WP devs can release code which can be downloaded, unzipped, uploaded to a server and then be involved in upgrading an existing WP install in such a way that requires no user intervention but which preserves all prior user changes, then they are living in cloudcuckoo land – it ain’t going to happen. 25,000 WP install as a minimum – do you honestly expect code to behave in a way other than generic ?

Anonymous, all you need to do is click the Publish button. The interface is not the clearest and I can understand your confusion, but don’t worry this is being improved in 1.3.
Also note that there’s a list of changed files on the wiki:
https://codex.www.ads-software.com/Changelog/1.2#Version_1.2.2

And if anyone thinks that the WP devs can release code which can be downloaded, unzipped, uploaded to a server and then be involved in upgrading an existing WP install in such a way that requires no user intervention but which preserves all prior user changes, then they are living in cloudcuckoo land – it ain’t going to happen.

i really didn’t see any posts suggesting that, but then i’m not very good at reading between the lines. i do think it’s probably more efficient for the devs to tell people what files have been changed than for every single hacker to generate their own diff between 1.2.1 and 1.2.2. i expect they are quite prepared to take the risk of generating errors, rather than wiping all their customisations every time there is a minor release.
anyway, my own issues are solved now — i have a copy of the trackback patch in case it wasn’t applied to the 1.2 branch, as well as the patch to fix the default status of posts. and i will be sure to record any other changes i make before 1.3.

i do think it’s probably more efficient for the devs to tell people what files have been changed than for every single hacker to generate their own diff between 1.2.1 and 1.2.2.

Which was my exact point from the beginning and why I wrote this post.
Thank you again,
Stu Schaff
Devsyn Development Studio

I’ll toss my 2 cents in – I only do minor modifications to WordPress, you know, to fix trackbacks and prevent spam, that sort of thing. I have no idea where you get this “diff” program, but the list of changed files above is immensely helpful.

On edit, self-deleted.

allusion, in the post above, already posted the address to the changelog. Sorry I missed it on the first quick read..