Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-pmc] Fwd: [eclipse-dev] 4.19 M2 whiteboard

So we have an agreement.
Target milestones are already created in bugzilla.

On Thu, Jan 21, 2021 at 3:59 PM Thomas Watson <tjwatson@xxxxxxxxxx> wrote:
+1 for adding M2 milestone.

Tom
 
 
 
----- Original message -----
From: Lars Vogel <lars.vogel@xxxxxxxxxxx>
Sent by: "eclipse-pmc" <eclipse-pmc-bounces@xxxxxxxxxxx>
To: eclipse-pmc@xxxxxxxxxxx
Cc:
Subject: [EXTERNAL] Re: [eclipse-pmc] Fwd: [eclipse-dev] 4.19 M2 whiteboard
Date: Thu, Jan 21, 2021 6:05 AM
 
+1, for adding M2 in bugzilla.

On Thu, Jan 21, 2021 at 12:59 PM Aleksandar Kurtakov
<akurtako@xxxxxxxxxx> wrote:
>
> Whole thread available at https://www.eclipse.org/lists/eclipse-dev/msg11594.html .
> My vote is for introducing M2 in bugzilla and stop using/requiring yet another unique step.
>
> ---------- Forwarded message ---------
> From: Александър Куртаков <akurtakov@xxxxxxxxx>
> Date: Thu, Jan 21, 2021 at 1:12 PM
> Subject: Re: [eclipse-dev] 4.19 M2 whiteboard
> To: General development mailing list of the Eclipse project. <eclipse-dev@xxxxxxxxxxx>
> Cc: Eclipse platform release engineering list. <platform-releng-dev@xxxxxxxxxxx>
>
>
>
>
> On Thu, Jan 21, 2021 at 1:10 PM Aleksandar Kurtakov <akurtako@xxxxxxxxxx> wrote:
>>
>>
>>
>> On Thu, Jan 21, 2021 at 1:07 PM Mickael Istria <mistria@xxxxxxxxxx> wrote:
>>>
>>>
>>>
>>> On Thu, Jan 21, 2021 at 11:45 AM Александър Куртаков <akurtakov@xxxxxxxxx> wrote:
>>>>
>>>> If we are to mark things for M2 we should just put it as a target milestone rather than introducing one more nonstandard way in our procedures.
>>>
>>>
>>> +1. What really matters with removal of M2 is that their is no dedicated build and related releng effort; if it's still useful for some to have a milestone definition, let's add one; as long as it doesn't re-introduce a freeze week and resource spent on delivering an extra milestone build.
>>
>>
>> Having bugzilla target for M2 is a standalone change that doesn't implicate anything else.
>
>
> Actually we shouldn't have skipped M2 in bugzilla at all and I still get questions why should I mark bugs for M3 when it will go out with M2.
>
>>
>>
>>>
>>> --
>>> Mickael Istria
>>> Eclipse IDE developer, for Red Hat Developers
>>> _______________________________________________
>>> eclipse-dev mailing list
>>> eclipse-dev@xxxxxxxxxxx
>>> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-dev
>>
>>
>>
>> --
>> Alexander Kurtakov
>> Red Hat Eclipse Team
>> _______________________________________________
>> eclipse-dev mailing list
>> eclipse-dev@xxxxxxxxxxx
>> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-dev
>
> _______________________________________________
> eclipse-dev mailing list
> eclipse-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-dev
>
>
> --
> Alexander Kurtakov
> Red Hat Eclipse Team
> _______________________________________________
> eclipse-pmc mailing list
> eclipse-pmc@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-pmc



--
Eclipse Platform project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com 
_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-pmc

 
 

_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-pmc


--
Alexander Kurtakov
Red Hat Eclipse Team

Back to the top