286275 - Status Update for 2.18.1 and 2.19.3

Status: RESOLVED FIXED

(Bugzilla :: bugzilla.org, defect, P1)

Description

[Max Kanat-Alexander]

So, we need a status update.

You'll probably want to mention our work on PostgreSQL support, and perhaps some
of the other cool stuff that has the relnote keyword on it.

If you do mention the PostgreSQL stuff, make sure that you include my warnings
from the email that I sent to developers@, about the fact that you CANNOT
UPGRADE from 2.19.3 on PostgreSQL to ANY OTHER RELEASE. You will have to drop
the database. We need to mention that everywhere that we mention Pg support.

Comment 1

[Jacob Steenhagen]

Still a work in progress, but here's the URL for what I have now just so it
doesn't get lost :)

Comment 2

[Max Kanat-Alexander]

Yeah, there is no 2.16.9. There will be, someday, if we ever feel like it, or if
there's a security problem to fix.

You might not even want to mention that 2.19.3 can create a database on
PostgreSQL, because it's unlikely that said database will be useful. :-) That
is, at this point you can't even enter a bug, although you *might* be able to do
some basic searches, and you can log in.

If you do tell them that they can create a Pg database, make sure you point them
at a link to bug 98304, so they can watch the blockers and patch their installation.

You might also want to mention that a lot of functions have moved and changed
their names, so customizers will want to be wary of that. Very little additional
moving or renaming should happen between here and 2.20, though.

One of the nice things to say about 2.18.1 is that 2.8 users can now upgrade,
though there are probably only four or five of those in the world. :-)

You might want to look at the URLs on the relnote bugs (bug 286273 and bug
286274) to pick out things that are significant enough to go in the release
notes, and thus might be worthy of a mention in the Status Update.

Comment 3

[Jacob Steenhagen]

(In reply to comment #2)
> You might not even want to mention that 2.19.3 can create a database on
> PostgreSQL, because it's unlikely that said database will be useful. :-) That
> is, at this point you can't even enter a bug, although you *might* be able to do
> some basic searches, and you can log in.

Well, this is a status update, not the release notes, so I think that mentioning
the status of our cross-db work is a good thing. I'll add a little more text
about how useless it currently is. Overall, however, it is a huge step in the
cross DB progess so I think it's worthy of mention.

> If you do tell them that they can create a Pg database, make sure you point them
> at a link to bug 98304, so they can watch the blockers and patch their
installation.

Will do.

> You might also want to mention that a lot of functions have moved and changed
> their names, so customizers will want to be wary of that. Very little additional
> moving or renaming should happen between here and 2.20, though.

I can do that, but I think that's much more important for the release notes.
Though the mention of probably statbility between now and release is important
for a status update.

Comment 4

[Max Kanat-Alexander]

It looks great, so far! :-)

Comment 5

[Mark Bickford]

Typo: under "Upcoming UI Hackathons", the link text "normal proceedures" should
be "normal procedures".

Comment 6

[Max Kanat-Alexander]

Published as part of bug 286271. Thanks, Jake! :-)