You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Carlos Santana <cs...@gmail.com> on 2013/10/17 21:17:51 UTC
What version to put when resolving jira issue for plugin?
It's not very clear what string to use when I fix a plugin
plugin have their own version
Could we add to CB Jira version strings for the plugins we support?
I was thinking something like this for every plugin
"org.apache.cordova.media@0.2.4"
"org.apache.cordova.media@0.2.5"
"org.apache.cordova.media@dev"
Then when I mark an issued revolved is very clear where the fix landed
--
Carlos Santana
<cs...@gmail.com>
Re: What version to put when resolving jira issue for plugin?
Posted by Andrew Grieve <ag...@chromium.org>.
Ah, I see what you mean - just put the version in a comment at the bottom.
That makes a lot of sense. Maybe just put in the version that's currently
reported in the repo (e.g. 0.2.4-dev)?
On Thu, Oct 17, 2013 at 3:42 PM, Carlos Santana <cs...@gmail.com>wrote:
> Yes I'm already doing that I put fixed version = 3.2.0 but wanted to add an
> additional version
>
> The bug was fix in plugin version "org.apache.cordova.device@0.2.4"
>
> Plugins have identifiers and versions, lets use them.
>
> Nothing about CLI, plugman the fix is not associated to any of those other
> components.
>
> See this for example:
>
> https://issues.apache.org/jira/browse/CB-5085?focusedCommentId=13798314&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13798314
>
> I will continue putting this level of details in the comments if the group
> doesn't mind, I think it makes more clear where is the fix located.
>
>
>
>
> On Thu, Oct 17, 2013 at 3:35 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
>
> > I think just mark them as the next cadence release (aka 3.1.0). It
> wouldn't
> > make sense to add versions of plugman & CLI & plugins. E.g. what would it
> > mean for a version to be marked as "released"? It may be released for one
> > plugin, but not another.
> >
> >
> > On Thu, Oct 17, 2013 at 3:17 PM, Carlos Santana <csantana23@gmail.com
> > >wrote:
> >
> > > It's not very clear what string to use when I fix a plugin
> > >
> > > plugin have their own version
> > >
> > > Could we add to CB Jira version strings for the plugins we support?
> > >
> > > I was thinking something like this for every plugin
> > >
> > > "org.apache.cordova.media@0.2.4"
> > > "org.apache.cordova.media@0.2.5"
> > > "org.apache.cordova.media@dev"
> > >
> > > Then when I mark an issued revolved is very clear where the fix landed
> > >
> > >
> > >
> > > --
> > > Carlos Santana
> > > <cs...@gmail.com>
> > >
> >
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>
Re: What version to put when resolving jira issue for plugin?
Posted by Carlos Santana <cs...@gmail.com>.
Yes I'm already doing that I put fixed version = 3.2.0 but wanted to add an
additional version
The bug was fix in plugin version "org.apache.cordova.device@0.2.4"
Plugins have identifiers and versions, lets use them.
Nothing about CLI, plugman the fix is not associated to any of those other
components.
See this for example:
https://issues.apache.org/jira/browse/CB-5085?focusedCommentId=13798314&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13798314
I will continue putting this level of details in the comments if the group
doesn't mind, I think it makes more clear where is the fix located.
On Thu, Oct 17, 2013 at 3:35 PM, Andrew Grieve <ag...@chromium.org> wrote:
> I think just mark them as the next cadence release (aka 3.1.0). It wouldn't
> make sense to add versions of plugman & CLI & plugins. E.g. what would it
> mean for a version to be marked as "released"? It may be released for one
> plugin, but not another.
>
>
> On Thu, Oct 17, 2013 at 3:17 PM, Carlos Santana <csantana23@gmail.com
> >wrote:
>
> > It's not very clear what string to use when I fix a plugin
> >
> > plugin have their own version
> >
> > Could we add to CB Jira version strings for the plugins we support?
> >
> > I was thinking something like this for every plugin
> >
> > "org.apache.cordova.media@0.2.4"
> > "org.apache.cordova.media@0.2.5"
> > "org.apache.cordova.media@dev"
> >
> > Then when I mark an issued revolved is very clear where the fix landed
> >
> >
> >
> > --
> > Carlos Santana
> > <cs...@gmail.com>
> >
>
--
Carlos Santana
<cs...@gmail.com>
Re: What version to put when resolving jira issue for plugin?
Posted by Andrew Grieve <ag...@chromium.org>.
I think just mark them as the next cadence release (aka 3.1.0). It wouldn't
make sense to add versions of plugman & CLI & plugins. E.g. what would it
mean for a version to be marked as "released"? It may be released for one
plugin, but not another.
On Thu, Oct 17, 2013 at 3:17 PM, Carlos Santana <cs...@gmail.com>wrote:
> It's not very clear what string to use when I fix a plugin
>
> plugin have their own version
>
> Could we add to CB Jira version strings for the plugins we support?
>
> I was thinking something like this for every plugin
>
> "org.apache.cordova.media@0.2.4"
> "org.apache.cordova.media@0.2.5"
> "org.apache.cordova.media@dev"
>
> Then when I mark an issued revolved is very clear where the fix landed
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>