Thanks Adrian. Your proposal makes sense. This is what I suspected. Cheers, Alexandre
On 13 Mar 2009, at 14:29, Adrian Lienhard wrote: > Some time ago we agreed that we use the Pharo issue tracker also for > packages included in the Pharo image (aka Pharo-dev). This is not > optimal, but there does not seem to be a much better solution right > now. > > But changes/fixes definitely don't belong into the Pharo(Inbox) > repository. For this one needs to check with the maintainers of the > package. > > Adrian > > On Mar 13, 2009, at 13:01 , Alexandre Bergel wrote: > >>> What I was told is pretty much summarized here: >>> http://code.google.com/p/pharo/wiki/HowToContribute >>> >>> In my words: >>> >>> 1. If your fix affects more than one Monticello package, create a >>> SLICE. >>> 2. Publish your SLICE or single package to the pharoinbox >>> repository. >>> 3. Create a google code issue >>> 4. Announce your change on this list! >>> >>> For some reason, it's kind of fun to watch it get loaded in an >>> upcoming update! >> >> My question is on Step 1. >> If the package is outside Pharo-Core and Pharo-Dev, then there is no >> reason to have it in PharoInbox and an issue on google. Everybody >> agree on that. If I modify Mondrian, there is no reason in polluting >> the Pharo community (beside some announcement of course :-). >> Now, the question is if the package is outside Pharo-Core, but >> included in Pharo-Dev. There is no sense in getting a fix in >> PharoInbox. However, shall the is...@google be created? >> >> If the package is within Pharo-Core, then the issue and the slide >> must >> be created. No doubt about that. >> >> Chers, >> Alexandre >> >>> >>> On Fri, Mar 13, 2009 at 4:36 AM, Alexandre Bergel <[email protected] >>>> wrote: >>> Hi All, >>> >>> I just make an enhancement of the SUnit support for OB. Shall I emit >>> an issue on google? I did so, but I just want to be sure. >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [email protected] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> [email protected] >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
