Post to Facebook
Tweet about this
Share at LinkedIn
Invite participants
Reference this page
Bernard - Sorry for the interruption, our Internet service provider has played with the back-end database server for about half-an-hour
Bernard - Hello Nick, the cPanel from Blue Host was reporting zero database for my account. What a shock!
How are you doing these days?
N1ckR - Busy busy busy. But not too bad really. Had a a few days off work this week, spent lots of time with my little daughter and looking at biggers houses to buy and thinking about installing linux again :D
Bernard - Spring time...
Not sure we will be so many tonight, so if there is some topic you would like to discuss with me, just let go...
Bernard - Yeap, this is the most important lack in the team at the moment
I would be ready to offer a place of associate at yetanothercommunitysystem.com for our next test manager, would you be interested?
N1ckR - Yes, of course, but we need to discuss strategy and how it fits in with release schedule and project management
Bernard - Major versions are due two times a year.
Next major release is planned for June, aka yacs 8.6.
AnsteyER - So the monthly updates will be bug-fixes mostly? and then the major updates will be more feature oriented?
Bernard - - Alpha versions can come at any time, and non-regression are minimal. Basically : capability to install a fresh server.
- Beta versions have more non-regression tests, and allow for upgrade, localisation is finalised, etc.
- Gamma versions have to be introduced to validate "stable" versions, two times a year.
Bernard - Normally, monthly releases are all at the beta level. But we need to work on gamma tests now to be ready by June...
Yes, Stephan, you are learning by experience
N1ckR - Bernard, if we plan on montly betas, then we need a stable branch that is gamma + bug fixes only.
Bernard - Nick, this should not be an issue thanks to the SVN system we have now at Google code. It's only a matter of organization.
Also, the idea is to stop new development on the monthly release that precedes a major version, to have only bugs fixed during one month.
For example, after the 8.5 due end of May all code changes would be dedicated to bug fixes before releasing the 8.6.
N1ckR - At some point we have to have a feature freeze to allow time for final testing before gamma release.
Touche Bernard !
Bernard - In my opinion, we can afford to stop development for one month, if this helps to limit the overhead on branch management, etc. This is the feature freeze you are talking about.
AnsteyER - That sounds like a prudent course. It insures that you regroup regularly and always have a recent stable version of the code to market.
N1ckR - I suppose we better stop talking about releases and ask if anyone has any problems or needs help with YACS ?
AnsteyER - Well.. most of my problems with YACS... relate to little things that frustrate, more than the code being bad.
AnsteyER - I was able to use the form tool with some effort. I have to finagle URLS or turn off the rewrite.
Hey Deb.
AnsteyER - Big problem on my site, now that emails are flowing again, is that members can't be grouped. And profiles can't be limited by Associates.
It'd be ideal for me to be able to send notices to 'poets' vs. 'writers'
or to create subscriptions
Bernard - Steve, you first have to create a form, and use the second tab to add fields on screen. Once a form has been created, it is visible in the overview at the Control Panel, and you can then use it to capture content.
AnsteyER - The content gets stored in a section as a page. It was fairly useful.
I'm actually going to use it to create a submission form for my contest.
Bernard - Steve, you can click on the 'Forms' link to access all forms, and then use the one you want.
Bernard - Steve, no problem, we are here to help.
Deb, the menu has the DOM id "main_menu", and this means you can make a lot of things with adequate CSS rules.
