Hi, Moriel.
Well, I see your point, but I still think it should be done. You spoke
about do this, do that, and I told, in one of the paragraphs, about the
case it isn't possible to reproduce the bug. So that what I suggest. Let's
decide that my proposition isn't rejected yet, but just stalled.
I see your idea here, Igal, but I don't think it's necessary.
Developers usually have pretty good tools to see where a bug came from (for
example, we have a tool called "git bisect"[1] that allows us to analyze
not just which release the bug was introduced in, but a specific commit to
"blame" for
The purpose is to say to developers if it's a new problem, or isn't. I can
think about six benefits:
1) It can save them the time for checking this.
2) It can be made better by task filer than by developer, because the first
knows better the problem.
3) It can save the time needed to them or other
If you don't have access to old mediawiki version (whether it is group2,
your own wiki or test3wiki suggested above),
and suspects there is a regression of something that was working in the
past,
it is useful to indicate it in the bug description, and the maintainer of
that feature can check it
>
> When filing a phab task with some new bug,
> you always want to know - is it really new, or I just did not pay attention
> to it before?
What's the purpose of this information? If it's a bug, new or not, a ticket
needs to be filed.
And when I do know it's a new bug, I can open both versions
It can work. But another Monday. I mean, if Tue-Wed-Thu there is a
deployment of version 5, a day before, Mon there is a deployment of
version 4, so starting from tomorrow, group 0 will get a way to see
both version, exactly from the beginning, but not until the end, for 6
days, group 1
No non-emergency deployments on Fridays, Saturdays or Sundays.
Monday could work.
-Chad
On Thu, Sep 21, 2017 at 7:15 PM יגאל חיטרון wrote:
> I glad you say so. What about Friday?
> Igal
>
>
> On Sep 22, 2017 05:07, "Chad" wrote:
>
> > It
I glad you say so. What about Friday?
Igal
On Sep 22, 2017 05:07, "Chad" wrote:
> It wouldn't be hard to do at all, technically. I imagine it'd be something
> like a test3wiki.
>
> Main thing to know is when do we cycle off of the old version? When the
> version goes
It wouldn't be hard to do at all, technically. I imagine it'd be something
like a test3wiki.
Main thing to know is when do we cycle off of the old version? When the
version goes out on Tuesdays? That day's already pretty loaded for software
moving about...
-Chad
On Thu, Sep 21, 2017 at 1:25 PM
I know this, of course. Our wiki is in group 1, and we reported a lot of
bugs in the first day. I'm talking about the case when you should file the
bug after Thursday.
Igal
On Sep 22, 2017 02:14, "Bryan Davis" wrote:
On Thu, Sep 21, 2017 at 2:52 PM, יגאל חיטרון
On Thu, Sep 21, 2017 at 2:52 PM, יגאל חיטרון wrote:
> Very well, thank you. And I thought it will not be a problem at all. But
> I'll try at least.
> -
> Hello, people! I believe you should think about a possibility of creation a
> new test wiki, that will be a
Very well, thank you. And I thought it will not be a problem at all. But
I'll try at least.
-
Hello, people! I believe you should think about a possibility of creation a
new test wiki, that will be a screenshot of deployments with one week
delay. So, every Thursday, at the moment
Making your case here is probably best. The release engineering team are
the people you probably have to convince, although of course anyone could
potentially create such a wiki, in an unofficial way.
Keep in mind that keeping an older version of the software running does
introduce a maintinance
Thank you. Sorry to hear this. Is there some place I can suggest this and
explain why do I think it can be very helpful?
Igal
On Sep 21, 2017 22:12, "Brian Wolff" wrote:
> On Thursday, September 21, 2017, יגאל חיטרון
> wrote:
> > Hi. Sometimes after
On Thursday, September 21, 2017, יגאל חיטרון wrote:
> Hi. Sometimes after the week deployment I need to compare the new version
> with the previous one, in some aspect. Is there a test wiki that always
has
> one version before the current?
> Thank you.
> Igal
Hi. Sometimes after the week deployment I need to compare the new version
with the previous one, in some aspect. Is there a test wiki that always has
one version before the current?
Thank you.
Igal (User:IKhitron)
___
Wikitech-l mailing list
16 matches
Mail list logo