Once Jan 1 comes around, it will be the end of an era and of course, the beginning of a new one.Īnyway, *if* you are interested in keeping those files, I’d suggest you download them as soon as possible. I guess it’s a feeling of nostalgia(makes me think of those years working with Callek to get the releases out on Buildbot) rather than actual utility. The copying is taking the longest.Īs the person who’ve worked on and around, I feel sad to see all those files go poof. At this point in time, I’m working on it. I’m hoping to setup the new storage system as a ‘static’ page so that one can just go to (for example, ) and you can see both the nightly and releases directory. Comm-* builds are no longer feasible/relevant. The rest will be “decommissioned” as they are relics of a past that we can no longer go back to. In order to upgrade from such an old version, install the last SeaMonkey 2.0 release first, do the one-time profile upgrade, uninstall SeaMonkey 2.0 and then install your target release (e.g. The only folders that are being migrated are the “releases” and nightly folder. SeaMonkey 2.53.7 will no longer offer to migrate your data from SeaMonkey 1.x or Mozilla 1.x at the first start after installation. It fixes some security issues and includes a few bug fixes. C:Program FilesSeaMonkey should be deleted also if left on disk before installing new. Hi All, This is a quick note that SeaMonkey 2.53.17.1 has been released. Board index SeaMonkey/Mozilla Suite SeaMonkey Builds. They will most likely be left as is until Mozilla blows it away (or I do). SeaMonkey 2.53.17.1 is out Posted on Septemby ewong. However, I want to note that there are files there that I will not be moving. So, we are migrating our files from to a storage system on Azure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |