As we move forward to the upcoming ClearOS 6.0 we are making beautiful strides with both the development environment and with the new tools which lend themselves for a better management experience for ClearOS. Guys, Peter and the whole development team are geniuses and the framework is beautiful. Importantly, the tools are coming together for better community input and the ability to make community contributed modules available. Included with this is the build system that will be able to crank out ClearOS 6.0 packages for both 32 and 64 bit ClearOS.
The big barrier at this point is the question of remaining dependent on the CentOS or creating ability to lay this framework directly on sources from Redhat. CentOS is scheduling their next release as 5.6 which will be the end of the 5.x series and represents the full maturation of the Redhat 5.x series. We plan on incorporating these improvements as updates/fixes to ClearOS 5.2. As far as we can tell, 6.0 is still on the long distance radar (I may be wrong on this and if I am, please let me know).
That being said, the release of CentOS 6.0 is not likely to happen until well after we are ready to release the new framework tools to the developer community. The code and kernel involved with 6.0 is significant because it contains many, many innovations and improvements that we would like to see and that we'd like to develop into the ClearOS 6.x branch.
The question for the community is what do you think??
We have some build resources that are coming together nicely and the questions are:
1) Now that we have the hardware and the infrastructure to do the raw work, should we commit some valuable time and resources to developing a ClearOS basic ISO that is a raw package libraries of rebuilt and sanitized RHEL (Redhat) 6.0, independent of CentOS?
2) Do we have sufficient community support and volunteers to do the necessary testing and QA on packages and code. (This adds a layer of complexity that is exciting, ambitious, liberating, scary, and causes serious trepidations.) Do we have enough community resources to make this happen?
3) Is there anyone in the general Linux community or the CentOS community that has some advice or directive that may prove useful in this crucial decision making process?
4) What does the end-user community feel? Is it worth the distraction?
Next week we have some serious grind to perform development-wise in the build platform so we need to make a decision by Thursday (Feb 17) of whether to proceed or not.
Please leave some comments and let us know how you feel. If you want to sign up to help, please click here
. If you need to send your comments anonymously or directly, please email me at dloper at <ThisDomain>.