WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Testing the Release Candidates  (Read 1486 times)

Offline rms46

  • Jr. Member
  • **
  • Posts: 60
    • Rahmat M. Samik-Ibrahim
Testing the Release Candidates
« on: October 14, 2012, 09:42:26 PM »
Quote
(from wiki)
We encourage people to download and install the release candidates, so you can help the Tinycore team, by testing them for improvements and bugs, before the final release.
The second release candidate of Core 4.7 is ready for public testing:[....]
Note: Requires new wbar.tcz and Xprogs.tcz (apps, scmapps, filetool) also in the rc testing area until final release.

Question: How dangerous is it to test release candidates by just replacing the "core.gz" file from version 4.6.2 to 4.7?

Thanks,
Rahmat.

This following is ROT13 -- Guvf sbyybjvat vf EBG13

Offline AbNoRMiS

  • Hero Member
  • *****
  • Posts: 550
  • nothing can be impeccable in this imperfect world
    • @ß№®M!$
Re: Testing the Release Candidates
« Reply #1 on: October 14, 2012, 10:40:49 PM »
if you are afraid then make backup and try update to new version
Basic Design Concept © @ß№®M!$
please forgive my terrible english :)

Offline althalus

  • Sr. Member
  • ****
  • Posts: 351
Re: Testing the Release Candidates
« Reply #2 on: October 15, 2012, 12:03:03 AM »
My experience has been that occasionally you run into small bugs in whatever new goodies the team have added, but never has a release candidate caused me any undue hassle. That said, they are testing versions, so backups are always a good idea.

I generally used to set up new versions as a separate entry in whichever boot loader  I was using at the time (so I'd have core.gz and core-3.1-rc1.gz for example), so I could easily switch between versions if needed, but I never needed to. The core team put out a very solid product.