ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

How do you handle build updates for clients

September 13, 2007 10:18am

Subscribe [10]
  • #16 / Sep 19, 2007 4:44am

    Thanks for the responses.
    I particularly like Kurt’s idea of a text file with notes about the installation.

    I suppose it comes down to how much the client is prepared to pay and the level of service they want. I think it would be good to offer an update/review package after 6 months say, to check all is OK.

    EDIT
    Interesting that after posting this I checked for build updates and there is quite a list of bug fixes, I would have thought that it was quite likely that existing installations would have come across some of these bugs and had a problem. Would this not reflect badly on the developer?

  • #17 / Sep 19, 2007 5:01am

    PXLated

    1800 posts

    I should elaborate a little more…One thing I like about using a Dev weblog within the site is you can pull up your notes from anywhere or any browser. Of course you need to create a Dev template. I usually lock that to super admins. If there are a lot of notes, I’ll categorize them like Kurt does in his list.

  • #18 / Sep 19, 2007 11:25am

    allgood2

    427 posts

    I use the same/similar method as PXLated and I like it a lot. Typically, when we are setting up a clients system, it means that we immediately add a developers weblog (I typically name them sysadmin or admin) and also secure access to just SuperAdmin and Admins.  I find the nice thing about this approach, beyond having web access to the data from where ever, is that it can handle more than update/upgrade notes, we also keep things like troublesome code, database admin notes, etc., etc.; or if there is a web dev group notices can be sent to all.

    I find it especially beneficial if there or more than one of us working on the client site; but very beneficial when its just me. In fact, when its just me, I think I store more code tidbits, because its nice to have them be searchable instead of having to remember what template did create that custom query on.

  • #19 / Sep 19, 2007 2:40pm

    Kurt Deutscher

    827 posts

    Hm. . . I really like the idea of a dev-weblog. . . it being viewable in a browser. . . and search-able. . . for project, template type notes, the idea works for me, but for software update notes, I like the idea of not counting on the software to be working during the update for me to see my notes.

    Also, and this is totally a personal thing, I don’t think I would remember to check a weblog post for notes when I’m using my FTP client. My brain needs a flashing red light attached to the system folder that says

    “Warning, have you thought through the implications of what you are about to do?”

    but that’s just me.

  • #20 / Sep 19, 2007 2:57pm

    PXLated

    1800 posts

    Kurt…Ya, for where I’ve hacked some files and need a reminder, I keep that in a text file like you and refer to it before I muck stuff up. I keep it locally but I think I’ll put a copy up on the server also.

  • #21 / Jun 24, 2008 10:18am

    Sean C. Smith

    3818 posts

    Just re-read this thread and have set up a word document for my current client with notes about the progress. If I hadn’t seen this again, I probably wouldn’t have done it and come to eventually regret not having the notes.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases