Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [rt-pmc] Vert.x 3.3 upcoming release stuck

This time of year is hard for IP reviews because of the impending release of the editor components which generally suck up all the air in the room.

That being said, if you have time issues on a certain CQ reaching out the to the IP team directly is absolutely a good way to approach it.

From the RT perspective, one thing that helps the RT projects is we decided on a meeting years ago that we were not going to bother with CQ's for strictly test or build dependencies, ie no need to mess with CQ'ing maven dependencies unless you are building a maven plugin.  Also test dependencies that will never see the light of day in anything released are good to go as well, for example I think we still have a jdbc session test using an in-memory database and we don't mess with having a CQ for that dependency.

Now if we offered that as something in the jetty-distribution that would be something that needed CQ'd, likely as a works with depending on how we did it.

cheers,
Jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx

On Fri, May 27, 2016 at 9:43 AM, Julien Viet <julien@xxxxxxxxxxxxxx> wrote:
2 months, that’s what I call agile.

> On May 27, 2016, at 4:30 PM, Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> wrote:
>
> From my experience, it's just a long queue. Thus, I try to have all CQs in around January/March timeframe for the annual June release. Two weeks is nothing for a CQ. Two months is a more realistic processing time.
>
> However, I do think there are changes being discussed. For example, with the ton of new IoT project coming to the Foundation I see a queue overload if *every* project has to submit their CQs.
>
> -Gunnar
>
> --
> Gunnar Wagenknecht
> gunnar@xxxxxxxxxxxxxxx, http://guw.io/
>
>
>
>
>
>
>> On 27 May 2016, at 00:47, Max Rydahl Andersen <manderse@xxxxxxxxxx> wrote:
>>
>> Hi rt-pmc,
>>
>> I would like to second Juliens concerns here. We've been submitting these IP reviews and I know the pmc have been diligent giving +1's but we keep getting stuck or stalled in the IP reviews.
>>
>> I'll do what I can to get IP team's attention, but I'm wondering how other components in the rt project handles this ? Are you just not updating or adding dependencies to your projects ?
>>
>> Asking since I would like to understand if vert.x is in unique situation or if I can bring other examples to the IP team to underline the importance of getting these things answered in a more timely manner.
>>
>> (btw. we are working on a proposal with the IP board on something that will most likely make this problem go away completely or almost completely - but until then we still need to actually get releases out.)
>>
>> Thank you,
>> Max
>>
>> Hi,
>>
>> we are going to release Vert.x 3.3 soon (a couple of weeks from now) and I we haven’t yet submitted yet the IPLog nor done the release review.
>>
>> The Netty 4.1.0.CR7 CQ has been submitted weeks ago (https://dev.eclipse.org/ipzilla/show_bug.cgi?id=11259) . Besides Netty 4.1.0.Final was released yesterday. I have no idea of the status of this CQ that has been submitted for ages  (why?)
>>
>> There is also a CQ for works-with dependencies that is unclear that it is cleared (https://dev.eclipse.org/ipzilla/show_bug.cgi?id=11379).
>>
>> So I haven’t been able to submit an IPLog because of this missing part.
>>
>> The release review is supposed to happen this week I think (last of may), but it is hard to know because I can’t find anymore such information on the website (why?)
>>
>> Anyway it would be awesome if we can move forward on this for the 3.3 release.
>>
>> thanks
>>
>> Julien
>> rt-pmc mailing list
>> rt-pmc@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/rt-pmc
>>
>> /max
>> http://about.me/maxandersen
>>
>> _______________________________________________
>> rt-pmc mailing list
>> rt-pmc@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/rt-pmc
>
> _______________________________________________
> rt-pmc mailing list
> rt-pmc@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/rt-pmc

_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/rt-pmc


Back to the top