[
https://issues.apache.org/jira/browse/THRIFT-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961357#comment-13961357
]
Mauro Maggi commented on THRIFT-1743:
-------------------------------------
I would go for B)
To avoid people from always depending on the trunk version, composer allows
this workflow:
- Use branch-aliasing on dev-master with an alias like "dev-master": current
stable tag (release) or branch
- Put composer.json in every tagged (release) branch without using
version/dev-alias directives
This way:
- people requiring dev-master will get latest dev commit
- people requiring the aliased branch will stay that way once dev-master gets
aliased to the next dev/release branch
- people requiring a specific tag/branch will stay unaffected
I don't know how releases/branch are worked on thrift (e.g. the 0.9.x. branch
is a year behind master), but the key idea is to use branch-aliasing on
dev-master to give people a way to safely require the release they want to rely
on.
> Add composer.json for new Symfony 2.1 Dependency Manager
> --------------------------------------------------------
>
> Key: THRIFT-1743
> URL: https://issues.apache.org/jira/browse/THRIFT-1743
> Project: Thrift
> Issue Type: Improvement
> Components: PHP - Library
> Affects Versions: 0.9, 1.0
> Reporter: Xavier HAUSHERR
> Assignee: Randy Abernethy
> Fix For: 0.9.2
>
> Attachments: composer.json, composer.master.json
>
>
> In order to use the new Symfony 2.1 Dependency Manager
> (http://getcomposer.org/), we have to add on root of Github project a file
> called composer.json with Composer configuration.
> This file must place in "/" in trunk and in 0.9x branch if possible.
> Is it possible to add this file ?
> Best regards.
> Xavier HAUSHERR
--
This message was sent by Atlassian JIRA
(v6.2#6252)
