[Pharo-users] How to contribute to Pharo Launcher?
tim at testit.works
Mon Jun 18 11:27:11 EDT 2018
Hi Cyril - I have to confess that I don’t recall what the steps are to safely commit in Monticello. I have smallish changes to 2 packages Core and Spec, and I can see that smalltalkhub repo in the MC browser and can browse my changes against it - but how do I commit both packages in there? I vaguely recall something about slices - but wasn’t that a Pharo core thing?
I get the impression that I don’t just press save on each package against sthub do I?
Sorry to be so dumb - I’ve just swapped out Monticello usage for Git usage these days. Just need a few hints to get back on track
> On 18 Jun 2018, at 16:20, Cyril Ferlicot D. <cyril.ferlicot at gmail.com> wrote:
> On 18/06/2018 17:15, Tim Mackinnon wrote:
>> Given Pharo Launcher is a bit in the limelight, I’m a bit nervous contributing blindly. Can someone point me/advice me towards how to safely push changes to StHub?
>> As I mentioned, I’ve added a last-modified column as well as fixing the broken status bar in PL (it looks like spec is a bit pernickety about nested tables).
> Since there is stable version released, you can safely commit in the
> StHub repository as long as you do not do a destructive actions such has
> deleting a .mcz from StHub.
> If the worst case, you will break the bleeding edge launcher, it will be
> detected by a review or a bleeding edge user and the commit will be
> either corrected or reverted.
> I think stable versions are created from the versions defined in
> Cyril Ferlicot
More information about the Pharo-users