The slots for the release managers need to be filled, please jump on it
Development wise I’ve tried to keep the same schedule as 9.0/2.3.0, which is not exactly what we planned, but seemed to work well and give us 4 months of effective develoment before the first beta
The slots for the release managers need to be filled, please jump on it
Development wise I’ve tried to keep the same schedule as 9.0/2.3.0, which is not exactly what we planned, but seemed to work well and give us 4 months of effective develoment before the first beta
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html
On Wed, Apr 3, 2013 at 9:25 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:
I volunteered for august last meeting. Schedule seems fine Andrea,
thanks for pushing. I advise us to tread lightly prior to foss4g.
I don't get the "tread lightly" part. Do you mean, relax the relases and
end up releasing the final after FOSS4G?
The current release schedule puts the final right in the FOSS4G days, while
this adds extra effort, it also makes
for extra splash during the presentations
I mean we should be aware people are busy with presentations and travel and may not be available for a QA push.
So lets try and do the QA push earlier than last time.
···
I volunteered for august last meeting. Schedule seems fine Andrea, thanks for pushing. I advise us to tread lightly prior to foss4g.
I don’t get the “tread lightly” part. Do you mean, relax the relases and end up releasing the final after FOSS4G?
The current release schedule puts the final right in the FOSS4G days, while this adds extra effort, it also makes
for extra splash during the presentations
