Mailing-List: contact dev-help@jmeter.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jmeter.apache.org
MIME-Version: 1.0
In-Reply-To: <CAH9fUpaE_y2MNm=mPxMRc7fvvUennvqg5uVpxSjpLGK_yYby-Q@mail.gmail.com>
References: <CAH9fUpZrK=3vmv3JKFw==cTtspgW2MiQvZ=fjDRuib_PDVbbLg@mail.gmail.com>
 <CAOGo0VbDjWN89kdjeRLyoWO32cinq-vJzocN7fgHT9cjEbE7SQ@mail.gmail.com>
 <A44309B7-B191-406B-9674-E254DE09F548@internetallee.de> <CAH9fUpaE_y2MNm=mPxMRc7fvvUennvqg5uVpxSjpLGK_yYby-Q@mail.gmail.com>
From: sebb <sebbaz@gmail.com>
Date: Sun, 26 Mar 2017 15:47:52 +0100
Message-ID: <CAOGo0VbOwdXftFxDcmDjK6XBGKtfkOk3Zd=SsbB=5xyjjpZY2A@mail.gmail.com>
Subject: Re: Bugzilla and nightly build
To: dev@jmeter.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
archived-at: Sun, 26 Mar 2017 14:47:58 -0000

I see.

The existing "Version" field is intended to record the version to
which the report applies.

There is also an advanced field (click on "Show Advanced Fields")
called "Target Milestone" whose hover text is:

"The Target Milestone field is used to define when the engineer the
bug is assigned to expects to fix it."

This field does not currently have any values, and I'm not sure it's
what is wanted.

AIUI what is being suggested is a field with the version which includes the=
 fix.
Let's call it "Fix version".

When a release has been made, that would be the actual release version.
Prior to that it would be the upcoming release version.

I'm not sure it's necessary to distinguish pending releases from
actual releases in Bugzilla.

It will be more work to maintain Bugzilla if snapshot releases are included=
.
Instead, the website links can just explain the process, i.e. the Fix
Version is the version of the release in which the fix is included,
and this may be a future release.
This is how many of the Commons components treat the JIRA "Fix version" fie=
ld.


On 25 March 2017 at 19:20, Philippe Mouawad <philippe.mouawad@gmail.com> wr=
ote:
> Hi,
> @Felix, you read correctly but the nighlty might be confusing if we forge=
t
> to move the fix version once we release
> Something like 3.2-SNAPSHOT might be clearer no?
>
> Regards
>
> On Saturday, March 25, 2017, Felix Schumacher <
> felix.schumacher@internetallee.de> wrote:
>
>>
>>
>> Am 25. M=C3=A4rz 2017 13:50:01 MEZ schrieb sebb <sebbaz@gmail.com
>> <javascript:;>>:
>> >On 25 March 2017 at 09:20, Philippe Mouawad
>> ><philippe.mouawad@gmail.com <javascript:;>> wrote:
>> >> Hello,
>> >> What do you think of adding to bugzilla a new field "FIX VERSION"
>> >which we
>> >> would use to indicate in which version bug is fixed (JIRA has such
>> >field).
>> >>
>> >> We could then use a search query to find all bugs fixed in any
>> >version but
>> >> also for upcoming release.
>> >> We could then put this link in Nightly build page so that users know
>> >what
>> >> bugs/enhancements nightly build version contains.
>> >>
>> >> I think it would also make it clear in which version a bug was fixed.
>> >>
>> >> We would also create new version soon in the process, either we call
>> >it
>> >> 3.2-nightly or 3.2 (but how to indicate that version is not released
>> >?).
>> >
>> >There are already nightly builds.
>> >The Maven ones use the name 3.2-SNAPSHOT, and the files themselves
>> >include a timestamp.
>> >The Jenkins ones only include the revision, but it should be easy
>> >enough to change that to include the target version number.
>> >The CI ones make be a bit more awkard to rename because the index page
>> >needs to be generated.
>>
>> I read it as Philippe meant to create tags to choose from in bugzilla. O=
n
>> the other hand, there is already a nightly tag, if I an not mistaken.
>>
>> Felix
>>
>> >
>> >Note that only builds which have been voted on may be promoted to the
>> >general public.
>> >
>> >>
>> >> If you're ok, do we have to ask for that to Infra team ?
>> >>
>> >>
>> >> Thanks
>> >> Regards
>> >> Philippe
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.