You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by Alessandro Molina <al...@ursacomputing.com> on 2021/07/02 09:05:53 UTC
Moving "Improvements" and "New Features" to 6.0.0 release
Hi everybody,
Given that the expected time for release 5.0.0 is approaching and there are
160+ Jira issues assigned to that release (
https://cwiki.apache.org/confluence/display/ARROW/Arrow+5.0.0+Release ) I'd
like to propose to do some cleanup of the TODO by bulk moving all 5.0.0
jira issues flagged as "Improvement" or "New Feature" to 6.0.0. That will
reduce the scope of Jira issues for 5.0.0 to ~30 bugs which seems a
more manageable goal.
If anyone has a new feature or improvement they are working on and want to
include in 5.0.0, those ones will obviously still be able to go. What I'm
proposing is just to move the issues by default and then in case anyone
wants to keep some of them in 5.0.0 they can be moved back.
In general if we move an issue you are involved on, you should receive a
notification and should be able to move it back to 5.0.0 if you want to
ship it in that release.
I hope this helps getting a better understanding of what's going to go in
5.0.0 so that release announcements can be more easily prepared
Any thoughts?
Re: Moving "Improvements" and "New Features" to 6.0.0 release
Posted by Alessandro Molina <al...@ursacomputing.com>.
I should have left all "In Progress" tasks assigned to 5.0.0, if you find
any task you want to release in 5.0.0 (I guess that means it should be
merged in the next 2 weeks) feel free to reassign it to 5.0.0
That moved the list of TODO tickets for 5.0.0 down to 57 issues (
https://cwiki.apache.org/confluence/display/ARROW/Arrow+5.0.0+Release )
On Sat, Jul 3, 2021 at 3:59 AM Weston Pace <we...@gmail.com> wrote:
> Can you leave the ones marked “in progress” or that have the
> pull-request-available label?
>
> On Thu, Jul 1, 2021 at 11:06 PM Alessandro Molina <
> alessandro@ursacomputing.com> wrote:
>
> > Hi everybody,
> >
> > Given that the expected time for release 5.0.0 is approaching and there
> are
> > 160+ Jira issues assigned to that release (
> > https://cwiki.apache.org/confluence/display/ARROW/Arrow+5.0.0+Release )
> > I'd
> > like to propose to do some cleanup of the TODO by bulk moving all 5.0.0
> > jira issues flagged as "Improvement" or "New Feature" to 6.0.0. That
> will
> > reduce the scope of Jira issues for 5.0.0 to ~30 bugs which seems a
> > more manageable goal.
> >
> > If anyone has a new feature or improvement they are working on and want
> to
> > include in 5.0.0, those ones will obviously still be able to go. What I'm
> > proposing is just to move the issues by default and then in case anyone
> > wants to keep some of them in 5.0.0 they can be moved back.
> >
> > In general if we move an issue you are involved on, you should receive a
> > notification and should be able to move it back to 5.0.0 if you want to
> > ship it in that release.
> >
> > I hope this helps getting a better understanding of what's going to go in
> > 5.0.0 so that release announcements can be more easily prepared
> >
> > Any thoughts?
> >
>
Re: Moving "Improvements" and "New Features" to 6.0.0 release
Posted by Weston Pace <we...@gmail.com>.
Can you leave the ones marked “in progress” or that have the
pull-request-available label?
On Thu, Jul 1, 2021 at 11:06 PM Alessandro Molina <
alessandro@ursacomputing.com> wrote:
> Hi everybody,
>
> Given that the expected time for release 5.0.0 is approaching and there are
> 160+ Jira issues assigned to that release (
> https://cwiki.apache.org/confluence/display/ARROW/Arrow+5.0.0+Release )
> I'd
> like to propose to do some cleanup of the TODO by bulk moving all 5.0.0
> jira issues flagged as "Improvement" or "New Feature" to 6.0.0. That will
> reduce the scope of Jira issues for 5.0.0 to ~30 bugs which seems a
> more manageable goal.
>
> If anyone has a new feature or improvement they are working on and want to
> include in 5.0.0, those ones will obviously still be able to go. What I'm
> proposing is just to move the issues by default and then in case anyone
> wants to keep some of them in 5.0.0 they can be moved back.
>
> In general if we move an issue you are involved on, you should receive a
> notification and should be able to move it back to 5.0.0 if you want to
> ship it in that release.
>
> I hope this helps getting a better understanding of what's going to go in
> 5.0.0 so that release announcements can be more easily prepared
>
> Any thoughts?
>