Updating on the updates..

Where are the updates?  It’s been so long… soo sooo long that I’ve forgotten when anyone got their browser updated automagically (as someone once said).

The release process is still half-manual half automatic.   I had hoped to make it totally automated; but we still have IanN and frg manually building them in a-manual-scripting method.    So that’s lacking; but it’s nearer than before.  Well, hell lot nearer than the updates situation.  No, that’s not saying a lot.  Kinda akin to starting a 10km hike and saying I’m near the finish line.  But it’s more like three quarters way to the destination.

As for the updates…  *sigh*.   I had thought I was nearly completed; but upon looking at the whole mess,  I’m far from completing.   Old versions and new versions.  Should we care about those using 2.0x?  What about 1.x?  At this point, I hate to say this but, those still using 1.x have no way of updating to whatever it is they can update to.   Even before this update process getting hosed,  1.x required manual updating to 2.x (read: Install anew).

So what about 2.0?  Then we have the issue of platform support.  Thanks to XP (and OSX Lion, and other old OSX systems) being de-supported, that adds a lot to what needs to be done.   Sounds kinda like ‘excusey’, I know.

The problem now boils down to what I want vs. what I can do with whatever time I can allot to dealing with this problem.

What I want:

I’d like to have an update system that can update whatever version to whatever *max* version that can be supported on the user’s system.    This is the most ideal setting.

What I can do:

Do we live in an ideal world?  No.   I feel the pressure.  I really do.  Psychologically I feel the anger and frustration.  I sense the pitchforks and the tar and feather.   I know they’re out to get me…

What I can’t do:

I unfortunately cannot set up updates for unsupported systems.  The obvious cases are for the OS/2s,  FreeBSDs,  and other systems I see checking for updates.   Yes, even Sunbird I can’t do anything about it.

Anyway…  I am currently working on the updates system.   I had hoped to build upon the old one (the pre-removal from Mozilla’s aus2 server) and while we did use it,   I had problems understanding the code.   So I built a newer system but due to the lack of concentration (haven’t been in the zone for a long time),  I couldn’t get things going.   Now, hopefully, I can concentrate on this.

I *really* need to get things working.  Those people with the pitchforks are gonna come for me.   Worst case scenario,  I get removed from the project and I’m relegated to peeling spuds  [which brings me to the name Spuds Mackenzie for some reason, but I digress].

Anyway, what I say here is wholy and solely my $0.02.  The other devs have nothing to do with this post.  So if the pitchforks do come…  the other devs have nothing to do with this….

Sometimes… I feel like “Arnold J. Rimmer” in Red Dwarf after the Astronavigation Exam where he’d stand up, does his curt double-rimmer salute to the examiner…  except.. his case, he says “I am a fish”…   I say, “I am an idiot.”   and then he passes out onto the floor.   I’m not yet there to passing out though.   So I guess…. nothing like him.    Now… Ace.. that’s someone I’d like to aspire to….  “Smoke me a kipper and I”ll be back for breakfast”

:ewong

 

 

 

About ewong

I'm a SeaMonkey dev/RelEnger and a bit of a buildbot dev.
This entry was posted in seamonkey. Bookmark the permalink.

6 Responses to Updating on the updates..

  1. deepsky says:

    Ewong,
    I wanted to give a small contribution to help supporting your efforts. I remember there was a donation link somewhere in the start page. I struggled to find it; it happens to be the ninth link in the side menu, buried among other way less important items. It looks life an afterthought and I doubt it is very successful as it is. You need a big, colorful call to action, well visible in the page. Volunteers are commendable, but paid developers are even better.

  2. Roger says:

    May I suggest starting with small steps? How about making 2.53.5 be able to update to 2.53.6? “Don’t let perfect be the enemy of good” and don’t use Rimmer’s revision timetable!
    Thank you for all that you do. Please don’t put too much pressure on yourself.

  3. Roger says:

    Sorry, I typoed my email address. Reposting with it corrected:

    May I suggest starting with small steps? How about making 2.53.5 be able to update to 2.53.6? “Don’t let perfect be the enemy of good” and don’t use Rimmer’s revision timetable!
    Thank you for all that you do. Please don’t put too much pressure on yourself.

  4. Serega011 says:

    We believe in you!

  5. xrror says:

    Who the heck is coming after you with pitchforks??? As a SeaMonkey user I’m just happy you’re keeping the project alive – auto-updates aren’t really a priority when I can just click the SeaMonkey logo in the upper right occasionally and see the release page…

    In the context of the project having to fundamentally rebuild itself after the collapse of the old build system + having to forge on w/o any really support from mozilla.org itself… auto-updates of all things seems such a minor “nice to have sometime” not “I’m going go skewer someone with a pitchfork” type of issue?

    • ewong says:

      Thanks for the comment. Pitchforks or not.. I realize (as frg always points out) it’s just software. I appreciate it very much. I am getting closer in having a ‘better’ update system.

Leave a Reply

Your email address will not be published. Required fields are marked *