Good news…bad news..

Not beating around the bush with this.  [wanted to have a catchy title… not being good with topics and all that, but.. no one cares about the title.  It’s the content..]

Well, the release will be done within this week, just not today (31st August 2015, PST(or whatever it is now)).  Really sorry about that.  I realize we said end of August, but … ok.  No buts.

Ok. There is a but.

But we are in the final stretch.  And of course, the disclaimer here is that ‘final’ is loosely termed as within this week (and dare I even say, ‘at the earliest’ – reason? .. oh you don’t want to know the excuses..  Would gremlins be satisfact… no? Um.. the dog?  umm the misalignment of… ).

The real reason is that with our infrastructure code, we don’t have the necessary infrastructure to support a testing environment.  So any changes we do to the infra code is live every time we post(and even though the infra code is reviewed, like everything else), there could be unforeseen circumstances that give our infra a fit.  (Yes. I know. In this day and age of DevOps and CI, this shouldn’t be the case; but, really..  the resources issue.  I’ve been planning to find a way to get some sort of CI/testing env for our infra code locally..  just haven’t been able to… work and family and other RL issues.)

So, please do bear with us just for a little bit longer.



PS: I realize this isn’t a proper PR ditty.  I’m not a PR person and therefore the aforementioned would probably get someone fired somewhere.  Anyway… no offense to anyone.   All I hope is that I can help this project in any way I can, even if it’s small.


About ewong

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

19 Responses to Good news…bad news..

  1. Marc says:

    Thanks for keeping up the work, it would really be a tragedy if Seamonkey died.
    Will any donations will help speeding up the release process for the future releases? Unfortunately I’m not deep enough in the software development in order to support the project with code.

  2. Ant says:

    Thanks for the updates and tedious work again. 🙂

  3. RickieES says:

    Being so close to solving one of our biggest problems for a long time is not something you should have to be sorry of. 🙂 Thanks a lot for all the time you’re putting into this.

  4. xrror says:

    Just wanted to pipe up also and say thanks for keeping the SeaMonkey flame burning. Don’t worry about the PR angle lol. It’s actually refreshing to some information on how broken things have gotten over the long years (!) mainly just due to lack of people/time. I’m just happy to have SeaMonkey lurch along at all these days =D

  5. Gabriele says:

    With this state of things, with better infrastructure nowhere near the sight, it might be better to turn to the cloud for testing etc.; it shouldn’t cost too much (of course you can ask for contributions) and ought to be easy to set up.

    By the way, this is the age of Continous Delivery rather than Continuous Integration. Looks like we are not quite there yet 🙂

Leave a Reply

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