Tech.Versionner History

Hide minor edits - Show changes to output

April 03, 2014, at 07:52 AM by 193.51.236.143 -
Changed lines 6-8 from:
* you have a development version that is a baseline. It means that a development version does not need to be updated to load latest versions of your project packages.
* a release is
a stable version and creates a version method. This way, all version methods of a configuration will be released versions of your software. In the future, Versionner will resolve all symbols for the version to have a reproductible loading. It also means that Versionner will prevent to release if one of your transitive dependencies is not specified as a fixed revision number. For these problems, semantic versionning may be a solution.
to:
* there is one and only one development version for your project (anytime). This development version is used to made changes to your project configuration. The release action (used to generate a numbered versions) rely on this development version.
* the development version is a baseline. It means that a development version does not need to be updated to load latest versions of your project packages.
*
a release is a stable version and creates a numbered version method. This way, all version methods of a configuration will be released versions of your software. Versionner allows you to solve symbolic versions of your dependencies (e.g. Foo #stable => Foo 1.3) at the release time. It enables reproductible loading of your project.
Changed line 72 from:
The release is done from the current development version. After the release, a new development version is automatically generated for you.
to:
The release is done from the current development version.
February 06, 2014, at 12:02 PM by 193.51.236.143 -
Changed line 77 from:
!!! Other actions
to:
!! Other actions
February 06, 2014, at 12:01 PM by 193.51.236.143 -
Changed lines 75-82 from:
You will be able to cherry pick changes and to commit them to their repositories.
to:
You will be able to cherry pick changes and to commit them to their repositories.

!!! Other actions
You also have some operations available from the contextual menu
* on the projects list
Path:/demarey/pmwiki/images/versionner/versionner-configlist-menu.png"Versionner projects menu"
* on the versions list
Path:/demarey/pmwiki/images/versionner/versionner-versionslist-menu.png"Versionner versions menu"
February 05, 2014, at 05:13 PM by 193.51.236.243 -
February 05, 2014, at 05:08 PM by 193.51.236.243 -
Added line 43:
To edit packages, use buttons on the top right corner of the list:
Added lines 45-46:
You can add / remove or edit packages.
The edition of a selected package allows you to update its requirements:
Added line 48:
Added line 50:
To edit dependent projects, use buttons on the top right corner of the list:
Added line 52:
When adding a dependent project, a first dialog asks you to select a configuration among those already loaded in the image.
Added line 54:
Then, you can specify the repository to use for this project (select a repository already declared in the image, edit one or create a new one).
Added lines 58-60:
To edit groups, use buttons on the top right corner of the list:
* to add a new group or
* to remove a group.
February 05, 2014, at 04:59 PM by 193.51.236.243 -
Deleted lines 30-34:
!!! Edit packages
!!! Edit dependent projects
!!! Edit groups
To add contents to a group, simply drag and drop items (packages, dependent projects) on it.

Added lines 41-53:

!!! Edit packages
Path:/demarey/pmwiki/images/versionner/versionner-packages-toolbar.png"Versionner packages toolbar"
Path:/demarey/pmwiki/images/versionner/edit-requirements.png"Versionner edit requirements"
!!! Edit dependent projects
Path:/demarey/pmwiki/images/versionner/versionner-dependant-projects-toolbar.png"Versionner dependent project toolbar"
Path:/demarey/pmwiki/images/versionner/add-required-project-1.png"Versionner add required project 1"
Path:/demarey/pmwiki/images/versionner/add-required-project-2.png"Versionner add required project 2"

!!! Edit groups
Path:/demarey/pmwiki/images/versionner/versionner-groups-toolbar.png"Versionner groups toolbar"
To add contents to a group, simply drag and drop items (packages, dependent projects) on it.
Path:/demarey/pmwiki/images/versionner/versionner-groups.png"Versionner groups"
February 05, 2014, at 04:44 PM by 193.51.236.243 -
Deleted lines 8-16:
To see detail on a project configuration, double-click on the project in the list, it will open a new window.
%center%Path:/demarey/pmwiki/images/versionner-project-list.png"Versionner project list" | '''Figure 1 : Versionner project list''

To add contents to a group, simply drag and drop items on it.
%center%Path:/demarey/pmwiki/images/versionner-osprocess-details.png"Versionner project details" | '''Figure 1 : Versionner project details''


''''+Here is a [[Versionner preview image->Path:/demarey/pmwiki/images/versionner-preview.zip]] you can play with.+''''

Deleted line 16:
Added lines 19-23:

You can display an existing configuration by double-clicking on it in the project list. It will open a new window.
%center%Path:/demarey/pmwiki/images/versionner-osprocess-details.png"Versionner project details" | '''Figure 1 : Versionner project details''

Added lines 30-34:

!!! Edit packages
!!! Edit dependent projects
!!! Edit groups
To add contents to a group, simply drag and drop items (packages, dependent projects) on it.
February 05, 2014, at 04:38 PM by 193.51.236.243 -
Changed lines 48-50 from:
to:
Clicking on Path:/demarey/pmwiki/images/versionner/versionner-save.png"Versionner save" will save the selected version by updating the current development version.
You are in development mode, no need to bloat the configuration with useless versions. You want to keep a version? What you need is to create a release.

Changed lines 52-54 from:
to:
Clicking on Path:/demarey/pmwiki/images/versionner/versionner-release.png"Versionner release" will create a release for your project, i.e. a numbered version with fixed packages version, that will be usable by others.
The release is done from the current development version. After the release, a new development version is automatically generated for you.

Changed lines 56-57 from:
Clicking on Path:/demarey/pmwiki/images/versionner/versionner-commit.png"Versionner commit"
to:
Clicking on Path:/demarey/pmwiki/images/versionner/versionner-commit.png"Versionner commit" will open the Kommiter tool. Kommiter will display the list of changes ONLY for your project, i.e. your project configuration and your project packages (as described in the latest version). Other changes will not be displayed.
You will be able to cherry pick changes and to commit them to their repositories.
February 05, 2014, at 04:04 PM by 193.51.236.243 -
Changed lines 47-52 from:
to:
!! Save a configuration

!! Release a version

!! Commit the project
Clicking on Path:/demarey/pmwiki/images/versionner/versionner-commit.png"Versionner commit"
February 05, 2014, at 03:59 PM by 193.51.236.243 -
Changed lines 31-33 from:
You will be first prompt the project name (without the ConfigurationOf prefix). Then, a window will pop-up showing an empty configuration.
You can now update your configuration
to:
You will be first prompt the project name (without the ConfigurationOf prefix).
Then, a window will pop-up showing an empty configuration.
You can now update your configuration.
%center%Path:/demarey/pmwiki/images/versionner/versionner-new-project.png"New project" | ''Figure 2 : New project''

Changed line 47 from:
WARNING
to:
February 05, 2014, at 03:56 PM by 193.51.236.243 -
Changed lines 30-45 from:
to:
Click on the "New project" button.
You will be first prompt the project name (without the ConfigurationOf prefix). Then, a window will pop-up showing an empty configuration.
You can now update your configuration

!! Update a configuration
The first thing to do is to select the version you want to edit in the versions list. Note that only the #stable and #development versions are displayed by default (tick the browse all box to see all versions).
You are now ready to edit the configuration.

'''WARNING''': you will loose your changes if you do not save before unselecting the current version.

* add packages (internal packages of your project),
* add dependent project (other projects you depend on). You need that the dependent project configuration is already available in the image.
* add groups,
* specify the project repository (use the button),

WARNING
February 05, 2014, at 03:02 PM by 193.51.236.243 -
Added line 27:
%center%Path:/demarey/pmwiki/images/versionner/versionner-project-list.png"Versionner project list" | ''Figure 1 : Versionner project list''
February 05, 2014, at 01:52 PM by 193.51.236.243 -
Added lines 17-29:

!! Open Versionner
You can find Versionner in the World menu / tools / Versionner.
The first window you will see displays the list of configurations currently loaded into the image. From here, you can:
* browse configurations
** with Versionner: double-click on a list item,
** with the System Browser: select a list item and press cmd+B
* create a new configuration,
* load an existing configuration.


!! Create a new configuration

July 26, 2013, at 08:34 PM by 128.93.179.68 -
Changed line 16 from:
'+Here is a [[Versionner preview image->Path:/demarey/pmwiki/images/versionner-preview.zip]] you can play with.+'
to:
''''+Here is a [[Versionner preview image->Path:/demarey/pmwiki/images/versionner-preview.zip]] you can play with.+''''
July 26, 2013, at 08:33 PM by 128.93.179.68 -
Changed line 16 from:
!! Here is a [[Versionner preview image->Path:/demarey/pmwiki/images/versionner-preview.zip]] you can play with.
to:
'+Here is a [[Versionner preview image->Path:/demarey/pmwiki/images/versionner-preview.zip]] you can play with.+'
July 26, 2013, at 08:33 PM by 128.93.179.68 -
Changed lines 15-16 from:
Here is a [[Versionner preview image->Path:/demarey/pmwiki/images/versionner-preview.zip]] you can play with.
to:

!!
Here is a [[Versionner preview image->Path:/demarey/pmwiki/images/versionner-preview.zip]] you can play with.
July 26, 2013, at 08:32 PM by 128.93.179.68 -
Changed lines 10-11 from:
to:
%center%Path:/demarey/pmwiki/images/versionner-project-list.png"Versionner project list" | '''Figure 1 : Versionner project list''
Added line 13:
%center%Path:/demarey/pmwiki/images/versionner-osprocess-details.png"Versionner project details" | '''Figure 1 : Versionner project details''
July 26, 2013, at 08:21 PM by 93.9.178.208 -
Added line 10:
July 26, 2013, at 08:20 PM by 93.9.178.208 -
Added line 9:
To see detail on a project configuration, double-click on the project in the list, it will open a new window.
July 26, 2013, at 08:20 PM by 93.9.178.208 -
Added lines 8-9:

To add contents to a group, simply drag and drop items on it.
July 26, 2013, at 03:13 PM by 193.51.236.243 -
Changed lines 7-9 from:
* a release is a stable version and creates a version method. This way, all version methods of a configuration will be released versions of your software. In the future, Versionner will resolve all symbols for the version to have a reproductible loading. It also means that Versionner will prevent to release if one of your transitive dependencies is not specified as a fixed revision number. For these problems, semantic versionning may be a solution.
to:
* a release is a stable version and creates a version method. This way, all version methods of a configuration will be released versions of your software. In the future, Versionner will resolve all symbols for the version to have a reproductible loading. It also means that Versionner will prevent to release if one of your transitive dependencies is not specified as a fixed revision number. For these problems, semantic versionning may be a solution.

Here is a [[Versionner preview image->Path:/demarey/pmwiki/images/versionner-preview.zip]] you can play with
.
July 26, 2013, at 01:52 PM by 193.51.236.243 -
Changed lines 1-7 from:
Versionner is a tool to manage project dependencies into [[Pharo|http://www.pharo-project.org/home]].
to:
Versionner is a tool to manage software dependencies into [[http://www.pharo-project.org/home|Pharo]].

Versionner can be seen as a GUI on top of Metacello to hide the complexity of ConfigurationOf objetcs.

Versionner makes some assumptions:
* you have a development version that is a baseline. It means that a development version does not need to be updated to load latest versions of your project packages.
* a release is a stable version and creates a version method. This way, all version methods of a configuration will be released versions of your software. In the future, Versionner will resolve all symbols for the version to have a reproductible loading. It also means that Versionner will prevent to release if one of your transitive dependencies is not specified as a fixed revision number. For these problems, semantic versionning may be a solution
.
July 26, 2013, at 12:36 PM by 193.51.236.243 -
Added line 1:
Versionner is a tool to manage project dependencies into [[Pharo|http://www.pharo-project.org/home]].