Hi all, Please keep in mind that your SLAs are not SLAs of the company in terms of Professional subscription contracts. Once you solve the bug, we must provide the solution to the partner. Many times it happens that a bug that should be released into the MPX should be postponed to the MPX+1 for some reason. In these cases, it is very important that CI is continously built so that support can provide our partners the obx before publication of next MP, and we can fulfill our contracts. In this case, March and April, a month has passed without a successful build, so it is very difficul for us to give a good service (in this case all SLA have been fulfilled and the service is not affected). Thanks.
Regards, Jon. On 16:24 Fri 16 Apr , Pablo Sarobe wrote: > Ok, thanks Dmitry > El 16/04/2010 15:51, Dmitry Mezentsev escribi�: > > Hi Pablo, > > According to my observations it should not affect SLA (might only > improve it:-). > > Nowadays we fix majority of OBPS feature in advance. Also for the > exceptions, as Ismael mentioned, urgent push to PI is still possible > but only under RM team moderation. > > From another side new policy is making > > * our recommended fixes delivery mechanism through MPs more stable, > > * and urgent fixes delivery mechanism through automatically generated > by CI OBX-es working more efficiently or just working (course if there > is no promotion to Main then this mechanism is just not working). > > Regards, > > Dmitry. > > 2010/4/16 Pablo Sarobe <[1][email protected]> > > What happens with the immediate issues? How could this affect SLA's? > Apart from that I agree > El 16/04/2010 12:42, Ismael Ciordia, Openbravo escribi�: > > 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 [2][email protected] 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 > > _______________________________________________ > [3]staff.qa mailing list > [4][email protected] > [5]http://list.openbravo.com/mailman/listinfo/openbravo.com.staff.qa > > _______________________________________________ > staff.engineering mailing list > [6][email protected] > [7]http://list.openbravo.com/mailman/listinfo/openbravo.com.staff.en > gineering > > References > > 1. mailto:[email protected] > 2. mailto:[email protected] > 3. http://staff.qa/ > 4. mailto:[email protected] > 5. http://list.openbravo.com/mailman/listinfo/openbravo.com.staff.qa > 6. mailto:[email protected] > 7. > http://list.openbravo.com/mailman/listinfo/openbravo.com.staff.engineering > _______________________________________________ > staff.engineering mailing list > [email protected] > http://list.openbravo.com/mailman/listinfo/openbravo.com.staff.engineering
------------------------------------------------------------------------------
_______________________________________________ Openbravo-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openbravo-development
