Re: [m2e-dev] m2e 1.1 endgame

[Andrew Eisenberg <andrew@xxxxxxxxxxxx>]

Oh well...I was hoping that the patch could be committed as long as
the code wasn't included in an official release, but re-reading [1]
looks like that's not the case.

I guess it will have to wait until SR1 to be released, but it would be
nice to get the IP process going quickly so that the code can be
included in dev builds as soon as possible post Juno.  This gives us
(SpringSource Tool Suite) the option to include the dev build in our
releases.

[1] http://wiki.eclipse.org/Development_Resources/Handling_Git_Contributions



On Sun, May 20, 2012 at 7:48 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
> I am not an expert on Eclipse IP process, but I believe any contribution
> larger than 250 LOC requires CQ and I we are well past any Juno CQ
> deadline as far as I know. I am willing to include this in Juno SR1 in
> September, even if this means doing another full m2e release, but
> I don't see how we can include this in Juno SR0.
>
> Again, not an expert on this stuff, so feel free to correct me if I
> misunderstand the "Eclipse way".
>
> --
> Regards,
> Igor
>
>
> On 12-05-20 4:29 PM, Andrew Eisenberg wrote:
>>
>> Getting everything done by May 23 will be tough.  I'll try, but there
>> may need to be a few more rounds of back and forth with patches.
>>
>> On Sun, May 20, 2012 at 11:34 AM, Fred Bricon<fbricon@xxxxxxxxx>  wrote:
>>>
>>> Igor,
>>>
>>> I really think you should include Andrew's work for
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=350414, provided he
>>> provides a
>>> proper patch before the deadline.
>>>
>>> Fred Bricon
>>>
>>>
>>> On Sun, May 20, 2012 at 8:01 PM, Igor Fedorenko<igor@xxxxxxxxxxxxxx>
>>>  wrote:
>>>>
>>>>
>>>> I am preparing m2e iplog for 1.1 release The deadline to submit iplog is
>>>> May 23/2012. We will not be able to accept any non-committer patches
>>>> until after 1.1 is out.
>>>>
>>>> I plan to publish m2e 1.1 rc1 build in next couple of days. Most likely
>>>> there will be no code changes compared to the current 1.1 snapshot build
>>>> available from [1], so you can start final 1.1 testing already.
>>>>
>>>> If you feel something absolutely has to be fixed in 1.1, please bring
>>>> this up here as soon as possible. Otherwise the current code will become
>>>> 1.1.
>>>>
>>>>
>>>> [1]
>>>>
>>>> https://repository.sonatype.org/content/repositories/forge-sites/m2e/1.1.0/N/LATEST/
>>>>
>>>>
>>>> --
>>>> Regards,
>>>> Igor
>>>> _______________________________________________
>>>> m2e-dev mailing list
>>>> m2e-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>>>
>>>
>>>
>>>
>>>
>>> --
>>> "Have you tried turning it off and on again" - The IT Crowd
>>>
>>> _______________________________________________
>>> m2e-dev mailing list
>>> m2e-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>>>
>> _______________________________________________
>> m2e-dev mailing list
>> m2e-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/m2e-dev
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-dev