Re: Upgrading guide
Lukas Kahwe Smith
On 28.01.2009, at 18:23, Steph Fox wrote:
> Yeah - as I said, this is a skeleton. I'll bring Pascal (and anyone
> else interested) into the loop for Round II, just interested in
> getting the basics in there @ present. Actually I'll just cc Pascal
> now :)
>
> I think we've missed some by the way - either that or there's some
> confusion regarding what should or shouldn't be in this file. But
> that's a matter for internals@ if we can't figure it out from
> previous 'upgrading' guides over the coming days/weeks. (Read: some
> people have been adding entries that I believe should probably go
> into 'NEWS' instead.)
Ok, I guess people should just jump on any section and start fleshing
them out. I guess a good idea would be to let people know when
starting on a section (unless its short enough to be started and
committed within a few hours).
regards,
Lukas Kahwe Smith
m...@pooteeweet.org
Steph Fox
> Ok, I guess people should just jump on any section and start fleshing
> them out. I guess a good idea would be to let people know when starting
> on a section (unless its short enough to be started and committed within
> a few hours).
Well don't get too carried away! We've a huge amount of... too much...
information to play with, to the extent that I'm wondering if we should
leave the 'new stuff to play with' for the release notes and NEWS file and
just concentrate on potential breakages in the UPGRADING file.
The original idea of having an upgrading file was that users (and primarily,
web hosting sysadmins) would have some kind of reference document so they'd
know what to expect on upgrade. Hannes went a bit mad and threw all the new
stuff into the second one (and probably the first one too, I forget now),
but I don't know that it really belongs there.
That said, Pascal's already given me a heap of notes to trawl through based
on the existing skeleton :)
- Steph
ps Please cc me in response, I don't subscribe to phpdoc ML.