Hi Richard,

Yes, thanks, good idea.
RM team is planning to have this metric. It will alarm us and trigger this
"logical freeze" cycles in future automatically.
Once we define the best implementation for it, we will announce it.


Regards,
Dmitry.


On 16 April 2010 12:55, Richard Morley <richard.mor...@openbravo.com> wrote:

>  Is there some way that we can get more visibility on this?
> Perhaps by adding a KPI to http://sites.google.com/site/obpsmeeting/?pli=1
> ?
> Regards
> Richard
>
>
> Ismael Ciordia, Openbravo wrote:
>
> Hi team,
>
> we have been for almost a month without a successful build in hudson and we
> can not afford it. In short release management will give as a new tool so we
> are able to do continuous integration testing in our repository before
> pushing to pi and it should solve the problem...
>
> But in the meantime we are gonna put an emmergency policy in place: Release
> Management team will do a "logical freeze" of pi code line after two days of
> failure in hudson. It means that they will send an email to all of us in
> this thread to notify this logical freeze. From that notification and till
> the problem is solved nobody can push to pi but to solve problems reported
> by continous integration. If during the freeze someone needs any
> other urgent push to pi -because whatever reason- they should coordinate
> with staff...@openbravo.com before doing that.
>
> So, all, please be aware that PI IS NOW FROZEN. Release management team
> will send us notification when it is again possible to push to main. Please
> take it very seriously.
>
> Thanks,
>
> Ismael
>
> ------------------------------
>
> _______________________________________________
> staff.engineering mailing 
> liststaff.engineer...@openbravo.comhttp://list.openbravo.com/mailman/listinfo/openbravo.com.staff.engineering
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Openbravo-development mailing list
> Openbravo-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openbravo-development
>
>
------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Openbravo-development mailing list
Openbravo-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openbravo-development

Reply via email to