Thanks @Rafael, That would really help.

On Fri, Mar 3, 2017 at 8:57 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:

> Tickets closed.
>
> Depending on the tickets, some I marked as closed, others as resolved. I
> also configured the status of some to invalid, others to incomplete, others
> as fixed.
>
> On Wed, Mar 1, 2017 at 5:07 PM, Rafael Weingärtner <
> rafaelweingart...@gmail.com> wrote:
>
> > Volks,
> >
> > It has been almost a week. I am assuming that no one knows about these
> > tickets.
> >
> > In the last years, our workflow has been improved greatly; most of the
> > PRs I see have Jira ticket associated and everything seems to be getting
> > better by the time. However, we have some (a lot?) Jira tickets that seem
> > to be left behind. I think a cleanup from time to time is a good thing.
> >
> >
> > In 48 ours I will close all of the tickets mentioned here. If I close
> > something that should not have been closed, please pardon me ;).
> >
> >
> >
> > After this, I will proceed with a new batch of tickets. Hopefully, in
> some
> > iterations of this process, we can get rid of these forgotten tickets.
> >
> > On Thu, Feb 23, 2017 at 3:16 PM, Rafael Weingärtner <
> > rafaelweingart...@gmail.com> wrote:
> >
> >> Thanks ;)
> >>
> >> On Thu, Feb 23, 2017 at 3:14 PM, Tutkowski, Mike <
> >> mike.tutkow...@netapp.com> wrote:
> >>
> >>> Thanks, Rafael. I uploaded an ISO and walked through the necessary
> parts
> >>> of the wizard. I agree with you that it has been fixed. I commented on
> the
> >>> ticket, then resolved and closed it just now.
> >>>
> >>> On 2/23/17, 12:46 PM, "Rafael Weingärtner" <
> rafaelweingart...@gmail.com>
> >>> wrote:
> >>>
> >>>     Thanks for taking time to look at this Mike.
> >>>     The ticket (CLOUDSTACK-4164
> >>>     <https://issues.apache.org/jira/browse/CLOUDSTACK-4164>) I managed
> >>> to
> >>>     check, and I believe it can be closed.
> >>>
> >>>     On Thu, Feb 23, 2017 at 2:39 PM, Tutkowski, Mike <
> >>> mike.tutkow...@netapp.com>
> >>>     wrote:
> >>>
> >>>     > Thanks for compiling this list, Rafael!
> >>>     >
> >>>     > I see I was the reporter for this issue:
> >>>     >
> >>>     > https://issues.apache.org/jira/browse/CLOUDSTACK-4164
> >>>     >
> >>>     > I plan to take a look at it and see what the current state is.
> >>>     >
> >>>     > On 2/23/17, 10:26 AM, "Rafael Weingärtner" <
> >>> rafaelweingart...@gmail.com>
> >>>     > wrote:
> >>>     >
> >>>     >     Hi folks,
> >>>     >     I have been reviewing old Jira tickets and we have a bunch
> >>> that can be
> >>>     >     closed. The following are the ones I have gone through.
> Before
> >>> I close
> >>>     > any
> >>>     >     ticket I would like to check them with you, especially the
> >>> ones from a
> >>>     >     category called “Seems to be fixed has to be checked”. I will
> >>> be
> >>>     > waiting
> >>>     >     for your feedback before I proceed to close any ticket.
> >>>     >
> >>>     >     - Have a title that does say much and the ticket does not
> have
> >>> a
> >>>     > detailed
> >>>     >     description
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-2225
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-917
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-947
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1259
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1441
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1576
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-2705
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-5793
> >>>     >
> >>>     >
> >>>     >     - Already solved
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-2532
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-6735
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-6837
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-7161
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-8202
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-8781
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-8817
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-9065
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1069
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1460
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1702
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1870
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-2075
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-2213
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-2439
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-6009
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-5219
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-4847
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-4778
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-4238
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-4164
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-4071
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-4055
> >>>     >
> >>>     >     - Seems to be fixed has to be checked (I did not have how to
> >>> check
> >>>     > these
> >>>     >     right now)
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-8873
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-8918
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-963
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1025
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1177
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1225
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1283
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1284
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1285
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1287
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1442
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1478
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1659
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-2215
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-2436
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-5225
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-4883
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-4440 (I
> >>> think
> >>>     > Nicolás
> >>>     >     may be able to help checking this one)
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-3784
> >>>     >
> >>>     >     - May be able to close after brief discussion/conversation
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-7819
> (are
> >>> we
> >>>     > supposed
> >>>     >     to be able to add tags to projects? Is it working right now?)
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1497 (Do
> >>> we want
> >>>     > to
> >>>     >     preserve alien VMs?)
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-1570 (I
> >>> did not
> >>>     >     understand if this is a feature that we already have and was
> >>> only
> >>>     > lacking
> >>>     >     documentation, or if it is a feature suggestion)
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-2535
> >>> (There is a
> >>>     >     discussion one person said some old configuration should be
> >>> removed and
> >>>     >     other said that they should now. However, the discussion
> >>> stopped
> >>>     > there; I
> >>>     >     think we can close this)
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-2616
> >>> (Database
> >>>     >     connection validation, do we have a config in our connection
> >>> pool to
> >>>     > keep
> >>>     >     those connections alive even when idle? Or at least recreate
> >>> them when
> >>>     > they
> >>>     >     expire?)
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-5550 (Is
> >>> this a
> >>>     >     problem? the keys are pretty big; I do not see the need to
> >>> fully
> >>>     > display
> >>>     >     the keys. A simple "shift + end" can be used to select the
> >>> keys and
> >>>     > copy
> >>>     >     them. Maybe a copy to transfer area button would be better?)
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-5182
> (The
> >>> pages
> >>>     > do not
> >>>     >     seem to exist anymore in new documentation page)
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-4018
> (User
> >>>     > entering
> >>>     >     invalid information regarding the environment, I do not see
> >>> this as a
> >>>     > bug
> >>>     >     (it is a user`s problem))
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-2785 (it
> >>> does not
> >>>     > seem
> >>>     >     to be a bug)
> >>>     >
> >>>     >     - Feature request that I did not understand the use and no
> one
> >>> seemed
> >>>     > to
> >>>     >     have worked on it
> >>>     >     -- https://issues.apache.org/jira/browse/CLOUDSTACK-8368
> >>>     >
> >>>     >     Thanks in advance for you future time and help ;)
> >>>     >
> >>>     >     --
> >>>     >     Rafael Weingärtner
> >>>     >
> >>>     >
> >>>     >
> >>>
> >>>
> >>>     --
> >>>     Rafael Weingärtner
> >>>
> >>>
> >>>
> >>
> >>
> >> --
> >> Rafael Weingärtner
> >>
> >
> >
> >
> > --
> > Rafael Weingärtner
> >
>
>
>
> --
> Rafael Weingärtner
>

Reply via email to