"Usama Dar" <munir.usama@gmail.com> writes: > i agree that release notes should not be too long, but may be there should > be (if there isn't one already) something like a "change log" where people > can find out all the changes done from the previous release, if they are > intrested ? The CVS history (either direct from the CVS server, or in the pgsql-committers archives) will give you as much detail as you could possibly want. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match

Josh Berkus <josh@agliodbs.com> writes: > I disagree. For people who want a quick summary of the major user-facing > things changed we'll have multiple sources: (a) the announcement, (b) the > press features list, (c) the Feature-Version matrix. The Release notes > should have a *complete* list of changes. Define "complete". > Why? Because we don't use a bug/feature tracker. So a user trying to > figure out "hey, was my issue XXX fixed so that I should upgrade?" has > *no other source* than the Release notes to look at, except CVS > history. And if we start asking sysadmins and application vendors to > read the CVS history, we're gonna simply push them towards other > DBMSes which have this information more clearly. So in other words, you don't *really* want "complete". This discussion is all about finding a suitable balance between length and detail. Simplistic pronouncements don't help us strike that balance. FWIW, I tend to agree with the folks who think Bruce trimmed too much this time. But the release notes are, and always have been, intended to boil the CVS history down to something useful by eliminating irrelevant detail. For the vast majority of people, the details that are being mentioned here are indeed irrelevant. There will be some for whom they are not. But depending on the question, almost any detail might not be irrelevant, and at that point you have to be prepared to go check the archives. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster

Heikki Linnakangas <heikki@enterprisedb.com> writes: > Dave Page wrote: >> That's inaccurate - I've been listed by full name for at least the last 3 or 4 releases. I realise I'm not the biggest contributor to the core code, but 'newer' certainly isn't right. > Maybe that's because you have such a short name. ;-) Yeah, laziness on the part of those preparing the release notes is certainly a factor ;-). I think when I did the first draft this time round, I wrote out Heikki's name in full the first time and then made it just "Heikki" thereafter. Perhaps a suitable solution would be to adopt that as formal policy --- it would solve the problem of bulk for heavy contributors while still treating everyone alike. Not sure about how to deal with first names that are enough alike to cause confusion, as in Dave vs David. When Tom Lockhart was around the project it was even messier, since he and I shared not only the same first name but all three initials. We got away with me being "Tom" and him "Thomas" for release-note purposes, but I think that only worked because we were both core members, so the case came up often enough to keep the distinction fresh in mind. (Or maybe everyone but the two of us was routinely confused...) Anyway, maybe a policy of "drop the last name on second and later mentions, unless this might cause confusion" would work. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate

Oleg Bartunov <oleg@sai.msu.su> writes: > On Mon, 10 Dec 2007, Bruce Momjian wrote: >> That is an excellent suggestion, done: >> >> Full text search is integrated into the core database >> system (Teodor, Oleg, Stefan Kaltenbrunner) > Wait, I think we need more words about original authors ! I agree, that is an *utterly* horrid change, as it makes it look like Stefan's contribution was of the same order of magnitude as Teodor's and Oleg's. I don't mind giving Stefan an appropriate amount of credit, but this is not it --- in fact, I read this as a direct insult to the two of them. They have spent years on tsearch; I doubt he spent more than a day. regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 7: You can help support the PostgreSQL project by donating at http://www.postgresql.org/about/donate

-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 > PostgreSQL two for the price of one. Postgre *and* SQL? :) - -- Greg Sabino Mullane greg@turnstep.com The first Postgres "Greg" (3 and counting now...) PGP Key: 0x14964AC8 200712101856 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iD8DBQFHXdJnvJuQZxSWSsgRAycCAJ4vTyEwvTT3saHa8Rbk3VSwSdirJgCfUrbr kzAjpXkRPOzyoghqFcu5NUM= =x7uc -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq