[Dextrose] New dextrose build!

[David Farning]

Excellent work on the builds .... but you know that you have been
doing them for weeks :)

Kudos on the build report. It is exactly what we need. I was able scan
the report in 30 seconds to get the executive summary for the company
for the week. Then the link to the build wiki let me dig into the
changes to understand who did what.... and what problem they were
trying to solve.

Some suggestions:
1. Can you Bcc this to our various  deployment support lists?
2. Can you synchronize build numbers across all builds?

While that might seem odd from a Release Management point of view it
with help deployments with the planning cycle.

The most common conversation I have usually goes something like this...

Deployment: We are 20 weeks from a release. Teachers want this.
Deployments support staff wants this. Management wants this.
Me: Ok 20 weeks out puts us after feature freeze so let's not try X,Y,
or Z. But A,B, and C look like they will fit well.
Deployment: OK we will make specifications for A,B, and C. but Y is
really important to us so we nee that too.
Me: Ok sounds good
Deployment: Good thanks

Wash, Rinse, and Repeat.

Ok, the conversation is a it more convoluted. It can take hours to
hash out what to include and what not to include.

A deployment must balance:
1 The needs and wants of the all share holders.
2. Bang for the bug of issue. They need to look at how much value a
fix will bring to them vs. the cost to fix it.
3. Risk/Reward. How great of risk a particular fix is with regard to
how likely it is to cause trouble. We are not going to do something
risky that can not be unwound close to a release.

On our side we must balance:
1. How does this affect all deployments. Is more than one deployment
interested, if so we can split the cost.
2. Do we have the available developers to work on that issue?
3. How does this affect upstream?

This all happens in the context of value:
1. A deployment must receive enough value from us to be willing to pay
for our services. We have no vendor lock. Everything we do is
opensource so they could do the work themselves with in-house staff.
2. We must charge enough to pay our staff reasonable wages.

So with that in mind. Can we take one step to reduce the confusions by
using consistent release numbers with each build increasing by one per
week. If we can't get there immediately that is understandable. There
are a lot of pieces moving right now. But let's set it as a goal to
start in a couple of weeks.

This way we can make it a bit easier to have the planning conversations.

David

On Mon, Jan 21, 2013 at 6:28 PM, Santiago Rodríguez
<scollazo at activitycentral.com> wrote:
> A new dextrose 4 build has been released, in our international , australian
> and uruguay flavours.
>
> Changes are as follow:
>
> International Edition ( Build 10)
>
> A11y fully supported on all builds
> Fix a bug in the .xsession handling, because we were ignoring previous
> content
>
>
> UY  ( Build 3 )
>
> Added libreoffice package (Fixes #2867)
> Added pnmixer package, but still no sound tray icon on gnome
> Fixed gconf keys not being applied (Fixes #2898)
> Added specific url for activities (Fixes #2873)
> Add a11y support to all builds (Fixes #2807)
> Fix a11y keyboard support (Fixes #2837)
> Updated ceibal-actualizador version to 3.0-10 (Fixes #2891)
> Refactorize package listings, so intead of having one different file for
> xo1.5-1.75-4 we have one on "gnome" section that fits all.
>
>
> AU Build 3
>
> Added maliit packages (Fixes #2896)
> Added specific url for activities (Fixes #2873)
>
> This changelog is based on http://sugardextrose.org/versions/122
>
> Builds can be found on http://198.27.75.136/dextrose/DX4/
>
>
> --
> Santiago Collazo
> Sysadmin
>
> Activity Central: http://activitycentral.com
>
> Facebook: https://activitycentral.com/facebook
> Google+: https://activitycentral.com/googleplus
> Twitter: https://activitycentral.com/twitter
>
> _______________________________________________
> Team mailing list
> Team at lists.activitycentral.com
> http://lists.activitycentral.com/listinfo/team
>



-- 
David Farning
Activity Central: http://www.activitycentral.com

Facebook: https://activitycentral.com/facebook
Google+: https://activitycentral.com/googleplus
Twitter: https://activitycentral.com/twitter