On Tue, Jun 14, 2011 at 9:33 AM, Marcus Denker <[email protected]>wrote:
> > On Jun 14, 2011, at 9:30 AM, laurent laffont wrote: > > > On Tue, Jun 14, 2011 at 9:06 AM, Miguel Moquillon < > [email protected]> wrote: > > Le 13/06/2011 17:57, Stéphane Ducasse a écrit : > > > > > > On Jun 13, 2011, at 9:09 AM, Miguel Moquillon wrote: > > > > Ok, > > > > I will extend SUnit to integrate my extensions. > > (It is unfortunate because there is just only one or two methods to > change.) > > > > so be ready that your code will not work when the next version of Sunit > show up. > > I really think that this is better to fork one version where we can do > what we want. > > Thus I have two possible solutions: > > - provide a direct contribution to the SUnit project with my code, > > - or fork SUnit to a new project (PharoUnit?) so that anybody can enhance > the unit test framework for Pharo. > > > > In fact, I don't know if the Pragma implementation in Pharo is specific > to the Squeak/Pharo smalltalk dialect. In that case, I think it would be > better to fork SUnit as my changes will be based upon pragmas. > > > > > > Indeed http://squeaksource.com/SUnit is global Read / Write, > creator/admin = Marcus Denker, so I suppose you can submit a package/branch > in this repo safely. > > > But keep in mind that the SUnit from Pharo is not regularly saved there... > maybe it should? But than, without automatisation this is too much work. > ok. Miguel, the right process may be: - fork SUnit in your own repo. - develop - once satisfied - open an issue - merge your SUnit in PharoCore - submit the slice in PharoInbox ? Laurent > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >
