WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Release candidates  (Read 2727 times)

Offline bmarkus

  • Administrator
  • Hero Member
  • *****
  • Posts: 7183
    • My Community Forum
Release candidates
« on: October 10, 2009, 03:47:04 AM »
I know this is a hard job to test releases, find and fix bugs, to make final release as bug free as possible as well as to meet schedules specially in a commercial development arena. The good point is that there are no such pressure on TC.

TC 2.4 development cycle was too fast in my view. 2.4 final followed 2.4rc5 in a very short time not leaving enough time for testing. Also it looks like (maybe I'm wrong) final 2.4 is not the same as 2.4rc5 If it is true, 2.4 is in fact 2.4rc6 and was released without wider testing.

Dear Robert and Core Team, my kind advice to slow down a bit and give more time to community for testing specially at the end of the cycle before the final release is out.

Regards... Béla
« Last Edit: October 10, 2009, 03:50:27 AM by bmarkus »
Béla
Ham Radio callsign: HA5DI

"Amateur Radio: The First Technology-Based Social Network."

Offline jls

  • Hero Member
  • *****
  • Posts: 2135
Re: Release candidates
« Reply #1 on: October 10, 2009, 04:07:15 AM »
maybe good to use also alpha before rc
dCore user

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: Release candidates
« Reply #2 on: October 10, 2009, 10:24:31 AM »
It did not seem to be any major changes from rc5 to final. We had been using rsync well before the failed cpio experment. But apparently a single character flag was omitted.

This ommision only affects tcz loaded onto the file system (ram) and only files with special flags setuid.
It is hard to be perfect. I never will be.

I am strongly considering inviting some of the more advanced community to participate in the private previews, as Team Tiny Core has lost half its size. The remaining team is quite stretched in our current project to transition to a single extension type.  Send me a PM if you would be interested in participating.

Another thing to consider, is that this project is going through a transistion to a single extension type.
It is not the normal feature enhancements and upgrades, instead it requires adjustments in all areas of the project, from base code, to extensions, to website, documentation etc....

Transitional periods are the most demanding, sometimes it is like juggling too many balls. Errors and ommisions will occur. On the other hand, prolonged transitional periods are not desireable by the developers nor I suspect the community.

I can only ask for understanding from the community during this period.
« Last Edit: October 10, 2009, 01:14:10 PM by roberts »
10+ Years Contributing to Linux Open Source Projects.

Offline bigpcman

  • Hero Member
  • *****
  • Posts: 719
Re: Release candidates
« Reply #3 on: October 12, 2009, 10:27:10 AM »


I am strongly considering inviting some of the more advanced community to participate in the private previews, as Team Tiny Core has lost half its size. The remaining team is quite stretched in our current project to transition to a single extension type.  Send me a PM if you would be interested in participating.


Who's gone? "Tiny Core has lost half its size"
big pc man

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: Release candidates
« Reply #4 on: October 12, 2009, 12:22:37 PM »
As it is surely obvious, the development side is strong as ever, with no slowdown.
However, the website, documentation, QA, and faq have seen little support.
Of course, users can and are contributiing to the Wiki.
10+ Years Contributing to Linux Open Source Projects.