I'm sorry if I've not been clear enought, but On Dec 13 2012, I annouved 
support for GPU in wizard AND DATABASE
http://sourceforge.net/mailarchive/message.php?msg_id=30224108 with no tech 
queries or warnings about this modification.

Then On January, 25 2013, I did announce that I would commit all my work 
http://sourceforge.net/mailarchive/message.php?msg_id=30401060 without 
receiving any warnings or advice.

I stated that I had tested the whole oscar on my cluster and that my 
modifications was able to pass all oscar steps including step 8. No more 
technical queries or warning.

Regarding the modification I madeto the database, there are several 
modifications level of danger.
Removing a column can be infinitely more harmfull that adding a column (our 
case). At worst, the added column is ignored. For GPU support, it was an 
addition.

Geoffroy, you know that I'm new to opensource developpement, so please, be a 
little bit more comprehensive with my mistakes.

Without my work, Oscar would still be stuck to RHEL5 wich entered Production2 
state on January 2013 (which means minor native hardware enhancements). As 
stated in this message 
http://sourceforge.net/mailarchive/message.php?msg_id=30401690 I know that 
while it works fine on my system, it is far to be ready for all systems and it 
may break things, but this is the way to go (on a developpent tree) if you want 
to reach the next step.

Best regards,

Olivier.

--
   Olivier LAHAYE
   CEA DRT/LIST/DCSI/DIR

________________________________________
De : geoffroy.val...@free.fr [geoffroy.val...@free.fr]
Date d'envoi : jeudi 31 janvier 2013 22:29
À : oscar-devel@lists.sourceforge.net
Objet : [Oscar-devel] Remark about any modification to the database

A modification to the database was made a few days ago, i am totally ok with 
that modification, but no developer is allowed to modify the database without 
initiating a discussion on the mailing list first. The database is the very 
core of OSCAR, we _must_ be very cautious with every single modification made 
the database schema and ensure that everybody in the project is ok with the 
proposed modification.

In other terms, like in any other project, for core modifications (such as the 
database), it is always better to send a RFC on the developer mailing list 
first, especially since we have a few active developers/maintainers again.

Thanks,

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Oscar-devel mailing list
Oscar-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oscar-devel

Reply via email to