{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihw5pv4plrw2md3kixqeiddotvtrtnpkkbsuldmqrwvimiyo6svay",
    "uri": "at://did:plc:hqad6xwuzg7oqfmwylfkvqfm/app.bsky.feed.post/3mmvmrz45nur2"
  },
  "path": "/viewtopic.php?t=33477&p=274795#p274795",
  "publishedAt": "2026-05-28T07:05:45.000Z",
  "site": "http://forum.palemoon.org",
  "textContent": "> Is it a \"portable\" type thing that's more or less self-contained\n\nPortables are provided (for Windows). You can use a separate profile in normal run operation as well. But see below with your other question:\n\n\n> Would I be given sites or a browser function to test against issues, as well my own perusing?\n\nNot really. RC testing is primarily to get some broader exposure prior to release in \"real world\" scenarios, i.e. normal day to day browsing. Depending on what has changed (preliminary release notes are posted as well) it allows you to spot-test some things but this isn't a strictly-organized beta program where you are asked to follow a rigid methodology (that has its own flaws, anyway, i.e. anything outside of the testing framework will be missed).\nSo you are basically asked to just use RCs \"as normal\"; they are built to be release-ready. It's mostly to catch any real showstoppers that might have slipped through in the dev cycle or regressed by it.\n\nDevtools, Windbg and crash dumps are normally not part of this \"last mile\" testing, but if you are familiar with the tools you can use them where prudent. FTP is available to upload crashdumps, see the \"howto\" post for that elsewhere on this board (don't have a link handy). So any appcrashes can be handled that way, if it's an issue.\n\n* * *",
  "title": "Browser Development • Re: Interested in being a pre-release tester? Apply here.",
  "updatedAt": "2026-05-28T07:05:45.000Z"
}