Slices and monticello - add to package... or add package to ... ? + procedure

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Slices and monticello - add to package... or add package to ... ? + procedure

philippeback
I was educating myself on slices. Maybe I'll be able to contribute a
bit properly one of these days.

Reading from http://code.google.com/p/pharo/wiki/HowToContribute.

Creating a slice in my own package-cache is all fine.

Now, to add it to the PharoInbox, I watched the screencast:
http://www.pharocasts.com/2010/03/how-to-contribute-to-pharo.html

There is this thing were we need to go to the PharoInbox repo in the
right pane on monticello.

The right click and select the Add to package.. option and then select
the slice.

All right, I can understand but this feels like unnatural to be on a
repository and ask to "Add to package..." where what I want to do is
to add the package to the repository.

I understand that this is required to have the repository associated
with the package so that I can save the package to one of its
associated repositories.

Maybe "Associate with package..." may be more helpful.

Also the procedure on HowToContribute is not right anymore. As the UI changed.

There is my version:

# How to make a slice

Slice: Your modification affect more than one package: you have to
create a SLICE package in your package cache
A SLICE is just a package with dependents ones, so you have to
indicate the dependent packages.

## Procedure
Open the Monticello browser.

You should see one or more packages marked as modified (they have an
asterisk before their name).

Select your package-cache repository on the right hand pane.

Create the new SLICE (click on the ''+SLICE'' button) and follow the
instructions.


### Old way
_Mark all_ the modified packages (the ones with asterisks before their
names) required by your SLICE package.

To do this, right click on the SLICE package in the left pane and
select ''add required package'', then select the package from the next
menu.

Repeat for all modified packages. (Yeah, boring)

### New way (Pharo 2.0 at least)
Put the issue tracker number in the Issue Number box and hit "Grab" to
get the title of the issue.
The (un)select in the list of "Dirty Packages to be included in the slice"

### Back to regular programming...

Select your package-cache repository, this will enable the save button.

Save the SLICE package (click on the ''Save'' button).

An mcz package will be saved in your cache for the SLICE package and
all the modified packages.
(Name: something along the lines of
SLICE-Issue-XXXX-YYYY-ZZZZ-Comment-Initials.1)

You will be prompted for a log message (for each one of them ?), type
a useful comment for the first package, (copy it and paste it on the
others - sure?).

Make sure to give the number of the issue your SLICE addresses in the comment.

Publish the package to PharoInbox repository.

# Hwo to publish to the PharoInbox repository

Open monticello.

Select the PharoInbox repository on the right pane.

Right click the repository and select "Add to package..." (this will
associate the package to the repository).

You'll be presented with a list of possible packages.

Pick up your slice.

Then, go back to Monticello Browser with a list of packages on the
left and a list of repositories on the right.

Select on your slice on the left.
Select the PharoInbox repository on the right.

Click the Save button on the top bar.

That's it, slice now in PharoInbox.


Phil

Reply | Threaded
Open this post in threaded view
|

Re: Slices and monticello - add to package... or add package to ... ? + procedure

Camillo Bruni-3
thanks! I'll try to update the entry in the wiki

On 2013-02-19, at 12:51, [hidden email] wrote:

> I was educating myself on slices. Maybe I'll be able to contribute a
> bit properly one of these days.
>
> Reading from http://code.google.com/p/pharo/wiki/HowToContribute.
>
> Creating a slice in my own package-cache is all fine.
>
> Now, to add it to the PharoInbox, I watched the screencast:
> http://www.pharocasts.com/2010/03/how-to-contribute-to-pharo.html
>
> There is this thing were we need to go to the PharoInbox repo in the
> right pane on monticello.
>
> The right click and select the Add to package.. option and then select
> the slice.
>
> All right, I can understand but this feels like unnatural to be on a
> repository and ask to "Add to package..." where what I want to do is
> to add the package to the repository.
>
> I understand that this is required to have the repository associated
> with the package so that I can save the package to one of its
> associated repositories.
>
> Maybe "Associate with package..." may be more helpful.
>
> Also the procedure on HowToContribute is not right anymore. As the UI changed.
>
> There is my version:
>
> # How to make a slice
>
> Slice: Your modification affect more than one package: you have to
> create a SLICE package in your package cache
> A SLICE is just a package with dependents ones, so you have to
> indicate the dependent packages.
>
> ## Procedure
> Open the Monticello browser.
>
> You should see one or more packages marked as modified (they have an
> asterisk before their name).
>
> Select your package-cache repository on the right hand pane.
>
> Create the new SLICE (click on the ''+SLICE'' button) and follow the
> instructions.
>
>
> ### Old way
> _Mark all_ the modified packages (the ones with asterisks before their
> names) required by your SLICE package.
>
> To do this, right click on the SLICE package in the left pane and
> select ''add required package'', then select the package from the next
> menu.
>
> Repeat for all modified packages. (Yeah, boring)
>
> ### New way (Pharo 2.0 at least)
> Put the issue tracker number in the Issue Number box and hit "Grab" to
> get the title of the issue.
> The (un)select in the list of "Dirty Packages to be included in the slice"
>
> ### Back to regular programming...
>
> Select your package-cache repository, this will enable the save button.
>
> Save the SLICE package (click on the ''Save'' button).
>
> An mcz package will be saved in your cache for the SLICE package and
> all the modified packages.
> (Name: something along the lines of
> SLICE-Issue-XXXX-YYYY-ZZZZ-Comment-Initials.1)
>
> You will be prompted for a log message (for each one of them ?), type
> a useful comment for the first package, (copy it and paste it on the
> others - sure?).
>
> Make sure to give the number of the issue your SLICE addresses in the comment.
>
> Publish the package to PharoInbox repository.
>
> # Hwo to publish to the PharoInbox repository
>
> Open monticello.
>
> Select the PharoInbox repository on the right pane.
>
> Right click the repository and select "Add to package..." (this will
> associate the package to the repository).
>
> You'll be presented with a list of possible packages.
>
> Pick up your slice.
>
> Then, go back to Monticello Browser with a list of packages on the
> left and a list of repositories on the right.
>
> Select on your slice on the left.
> Select the PharoInbox repository on the right.
>
> Click the Save button on the top bar.
>
> That's it, slice now in PharoInbox.
>
>
> Phil
>


Reply | Threaded
Open this post in threaded view
|

Re: Slices and monticello - add to package... or add package to ... ? + procedure

Sean P. DeNigris
Administrator
In reply to this post by philippeback
Thanks for updating this, phil!

philippeback wrote
I was educating myself on slices. Maybe I'll be able to contribute a
bit properly one of these days.
It's actually sooo easy now... much has been streamlined...

philippeback wrote
All right, I can understand but this feels like unnatural to be on a
repository and ask to "Add to package..." where what I want to do is
to add the package to the repository.
I agree that this part of the UI is counter-intuitive, but the good news is, you don't have to do this step for slices anymore. The inbox is added automatically.

philippeback wrote
Select your package-cache repository on the right hand pane.
This step is no longer necessary.

philippeback wrote
You will be prompted for a log message (for each one of them ?)
There's just one commit message for the whole slice.

philippeback wrote
Make sure to give the number of the issue your SLICE addresses in the comment.
Interesting. I never do that. Why is it necessary?

philippeback wrote
Right click the repository and select "Add to package..." (this will
associate the package to the repository).
Again, not necessary.

Also, why save to the package cache first? I always save directly to the inbox and I'm pretty sure is automatically saves to the cache as well...

Cheers,
Sean
Cheers,
Sean