cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filip Maj (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CB-12537) plugins releaser should work with brand new plugins repositories instead of dev's working repos
Date Fri, 03 Mar 2017 23:01:45 GMT

     [ https://issues.apache.org/jira/browse/CB-12537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Filip Maj updated CB-12537:
---------------------------
    Description: 
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

  was:We don't want to be munging dev repo states destructively. Better to set aside fresh
clones. Might take a while though :/


> 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: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org


Mime
View raw message