spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Rosen <rosenvi...@gmail.com>
Subject Re: Sidebar: issues targeted for 1.4.0
Date Tue, 16 Jun 2015 15:09:22 GMT
Whatever you do, DO NOT use the built-in JIRA 'releases' feature to migrate
issues from 1.4.0 to another version: the JIRA feature will have the
side-effect of automatically changing the target versions for issues that
have been closed, which is going to be really confusing. I've made this
mistake once myself and it was a bit of a hassle to clean up.

On Tue, Jun 16, 2015 at 5:24 AM, Sean Owen <sowen@cloudera.com> wrote:

> Question: what would happen if I cleared Target Version for everything
> still marked Target Version = 1.4.0? There are 76 right now, and
> clearly that's not correct.
>
> 56 were opened by committers, including issues like "Do X for 1.4".
> I'd like to understand whether these are resolved but just weren't
> closed, or else why so many issues are being filed as a todo and not
> resolved? Slipping things here or there is OK, but these weren't even
> slipped, just forgotten.
>
> On Sat, May 30, 2015 at 3:55 PM, Sean Owen <sowen@cloudera.com> wrote:
> > In an ideal world,  Target Version really is what's going to go in as
> > far as anyone knows and when new stuff comes up, we all have to figure
> > out what gets dropped to fit by the release date. Boring, standard
> > software project management practice. I don't know how realistic that
> > is, but, I'm wondering how people feel about this, who have filed
> > these JIRAs?
> >
> > Concretely, should non-Critical issues for 1.4.0 be un-Targeted?
> > should they all be un-Targeted after the release?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
> For additional commands, e-mail: dev-help@spark.apache.org
>
>

Mime
View raw message