Skip to content

Commit

Permalink
Merge pull request #102 from akeneo/prepare-alpha3
Browse files Browse the repository at this point in the history
Prepare 1.0.0-alpha3
  • Loading branch information
LaurentPetard authored Oct 13, 2017
2 parents 3b4b226 + 48ac90a commit cf01888
Show file tree
Hide file tree
Showing 2 changed files with 29 additions and 1 deletion.
14 changes: 14 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,17 @@
# 1.0.0-alpha3

## Improvements

- MIG-1 Migration of products variations from InnerVariationBundle
- MIG-71 SSH with passphrase
- MIG-69 PIM 2.0.2 compatibility

## Bug fixes

- GITHUB-93 Fix destination pim version check
- GITHUB-89 Error when reading Composer repositories
- GITHUB-95 Fix SshConsole constructor

# 1.0.0-alpha2

## Improvements
Expand Down
16 changes: 15 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,9 +60,21 @@ Enterprise | Published Product | WIP |
Extension | Version |
--------------------- | ------------------------------------------------------------- |
ElasticSearchBundle | Not relevant as ElasticSearch is now part of the native stack |
InnerVariationBundle | WIP to transform variations to models |
InnerVariationBundle | 1.0.0-alpha3 |
CustomEntityBundle | WIP |

#### InnerVariationBundle

The modeling of the variations with the IVB must be well structured to be fully handled by Transporteo. In the PIM 2.0, a family variant can't have more than 5 axis, and this axis should be one of the following types:
- Simple select
- Reference data simple select
- Metric
- Yes/No

If one these conditions is not fulfilled, the products concerned won't be migrated. You will have to think about a better modeling for these products and migrate them manually.

You can find the details of the errors in the file "var/logs/error.log".

### Custom Code

For now, the custom code migration is not automated.
Expand Down Expand Up @@ -111,6 +123,8 @@ You will have to migrate it following this [upgrade file](./UPGRADE-2.0.md).

We plan to automate this part in future release, stay tuned ! :)

*Tip: You can define the default responses in the file "src/Infrastructure/Common/config/parameters.yml"*

## How to contribute

Please, have a look on the [CONTRIBUTING](./.github/CONTRIBUTING.md) page.
Expand Down

0 comments on commit cf01888

Please sign in to comment.