[
https://issues.apache.org/jira/browse/CB-12537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895492#comment-15895492
]
ASF subversion and git services commented on CB-12537:
------------------------------------------------------
Commit f73674e47daf38825fb2d5413baba86f7737657a in cordova-coho's branch
refs/heads/plugins-releaser from filmaj
[ https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;h=f73674e ]
CB-12537: Give RM option of using a fresh working directory to clone repos in.
> plugins releaser should work with brand new plugins repositories instead of
> dev's working repos
> -----------------------------------------------------------------------------------------------
>
> Key: CB-12537
> URL: https://issues.apache.org/jira/browse/CB-12537
> Project: Apache Cordova
> Issue Type: Sub-task
> Components: Coho
> Reporter: Filip Maj
> Assignee: Filip Maj
>
> We don't want to be munging dev repo states destructively. Better to set
> aside fresh clones. Might take a while though :/
> What if the flow was composed of two parts? Like so:
> 1. A 'should I auto-detect which plugins need a release, or do you want to
> specify those manually?' question
> 2. A 'do you want me to use an existing working directory of plugin repos, or
> should i clone them fresh?' question
> Then the resulting four options are:
> - need to work with an existing set of repos, and update the repos, and
> auto-detect which ones need a release
> - need to work with an existing set of repos, but want to manually specify
> which plugins to release, and only update those
> - need to create a new directory, clone all the plugin repos, and
> auto-detect which ones need a release
> - need to create a new directory and clone only the specified plugins to
> release
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
