Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-planning-council] Fwd: [cross-project-issues-dev] Request to respin Oxygen.2 packages to include m2e 1.8.2

On Tue, Dec 12, 2017 at 4:52 PM, Frederic Gurr
<frederic.gurr@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> Hi,
>
> To speed-up the process, I'm posting this request to the Planning
> Council mailing list.
>
> I assume there will be no vetos, therefore I've already started the
> process (I can still stop/revert it).

Downgrade is smth that shouldn't happen for sure.

>
> Regards,
>
> Fred
>
>
> --
> Frederic Gurr
>
> Release Engineer
> Eclipse Foundation
>
>
> -------- Forwarded Message --------
> Subject:        [cross-project-issues-dev] Request to respin Oxygen.2 packages
> to include m2e 1.8.2
> Date:   Mon, 11 Dec 2017 08:56:22 -0500
> From:   Fred Bricon <fbricon@xxxxxxxxx>
> Reply-To:       Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
> To:     technology-pmc@xxxxxxxxxxx, Cross project issues
> <cross-project-issues-dev@xxxxxxxxxxx>
>
>
>
> Dear Technology PMC,
>
> the current Oxygen.2 RC4 packages contain m2e 1.8.1 from Oxygen.1,
> instead of the 1.8.2 release which was contributed in Oxygen.1a.
>
> 1.8.2 contains a number of fixes related to Java 9 support[1] and
> shipping 1.8.1 instead would be a serious regression from a usability
> perspective.
>
> Can we please bring this forward to the Planning Council to request a
> respin of the Oxygen.2 release? It's unclear to me if I should open a BZ
> for this request, let me know and I'll make it happen if needed.
>
> Thanks in advance,
>
> Fred
>
> [1] https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&classification=Technology&columnlist=target_milestone%2Ccomponent%2Cassigned_to%2Cresolution%2Cshort_desc%2Cchangeddate&known_name=m2e%201.7&list_id=17047887&product=m2e&query_based_on=m2e%201.7&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&resolution=NOT_ECLIPSE&target_milestone=1.8.2%2FOxygen.1a%20RC1&target_milestone=1.8.2%2FOxygen.1a%20RC2
> <https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&classification=Technology&columnlist=target_milestone%2Ccomponent%2Cassigned_to%2Cresolution%2Cshort_desc%2Cchangeddate&known_name=m2e%201.7&list_id=17047887&product=m2e&query_based_on=m2e%201.7&query_format=advanced&resolution=---&resolution=FIXED&resolution=INVALID&resolution=WONTFIX&resolution=DUPLICATE&resolution=WORKSFORME&resolution=MOVED&resolution=NOT_ECLIPSE&target_milestone=1.8.2%2FOxygen.1a%20RC1&target_milestone=1.8.2%2FOxygen.1a%20RC2>
>
> On Mon, Dec 11, 2017 at 3:51 AM, Markus Knauer
> <mknauer@xxxxxxxxxxxxxxxxx <mailto:mknauer@xxxxxxxxxxxxxxxxx>> wrote:
>
>     Hi Fred,
>
>     you should consider asking your PMC and on cross-project-issues-dev
>     for a respin [1]. It is not as complicated as it sounds, and this
>     issue is probably worth fixing it.
>     As soon as the Oxygen.2 respin is done, we can rebuild the packages.
>
>     [1]
>
> https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements/Appendix#Planning_Council_Exception_Process
>
> <https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements/Appendix#Planning_Council_Exception_Process>
>
>
>     Thanks and regards,
>     Markus
>
>
>     On 8 December 2017 at 14:24, Fred Bricon <fbricon@xxxxxxxxx
>     <mailto:fbricon@xxxxxxxxx>> wrote:
>
>         Sorry, I guess this one's on me.
>
>         I fixed the simrel contribution[1], so it's ready for a respin,
>         should you decide to go for it.
>
>         Fred
>
>
> [1] http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?h=Oxygen_update&id=9a236ebb7ad09ba3771370c30e2dbe475b6f188b
>
> <http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?h=Oxygen_update&id=9a236ebb7ad09ba3771370c30e2dbe475b6f188b>
>
>         On Fri, Dec 8, 2017 at 8:02 AM, Andreas Sewe
>         <andreas.sewe@xxxxxxxxxxxxxx
>         <mailto:andreas.sewe@xxxxxxxxxxxxxx>> wrote:
>
>             Hi again,
>
>             > So, the changes made for the Oxygen.1a_respin never made
> it into
>             > Oxygen_update.
>
>             opened a bug with the m2e project [1] for discussion of the
>             *technical*
>             side of things. Whether to respin or not, however, is a
>             discussion
>             better left to this list or cross-project-issues, I think.
>
>             Best wishes,
>
>             [1] <https://bugs.eclipse.org/bugs/show_bug.cgi?id=528320
>             <https://bugs.eclipse.org/bugs/show_bug.cgi?id=528320>>
>
>             --
>             Codetrails GmbH
>             The best code possible
>
>             Robert-Bosch-Str. 7, 64293 Darmstadt
>             Phone: +49-6151-276-7092 <tel:%2B49-6151-276-7092>
>             Mobile: +49-170-811-3791 <tel:%2B49-170-811-3791>
>             http://www.codetrails.com/
>
>             Managing Director: Dr. Marcel Bruch
>             Handelsregister: Darmstadt HRB 91940
>
>
>             _______________________________________________
>             epp-dev mailing list
>             epp-dev@xxxxxxxxxxx <mailto:epp-dev@xxxxxxxxxxx>
>             To change your delivery options, retrieve your password, or
>             unsubscribe from this list, visit
>             https://dev.eclipse.org/mailman/listinfo/epp-dev
>             <https://dev.eclipse.org/mailman/listinfo/epp-dev>
>
>
>
>
>         --         "Have you tried turning it off and on again" - The IT
> Crowd
>         And if that fails, then http://goo.gl/tnBgH5
>
>         _______________________________________________
>         epp-dev mailing list
>         epp-dev@xxxxxxxxxxx <mailto:epp-dev@xxxxxxxxxxx>
>         To change your delivery options, retrieve your password, or
>         unsubscribe from this list, visit
>         https://dev.eclipse.org/mailman/listinfo/epp-dev
>         <https://dev.eclipse.org/mailman/listinfo/epp-dev>
>
>
>
>
>     _______________________________________________
>     epp-dev mailing list
>     epp-dev@xxxxxxxxxxx <mailto:epp-dev@xxxxxxxxxxx>
>     To change your delivery options, retrieve your password, or
>     unsubscribe from this list, visit
>     https://dev.eclipse.org/mailman/listinfo/epp-dev
>     <https://dev.eclipse.org/mailman/listinfo/epp-dev>
>
>
>
>
> --
> "Have you tried turning it off and on again" - The IT Crowd
> And if that fails, then http://goo.gl/tnBgH5
>
> _______________________________________________
> eclipse.org-planning-council mailing list
> eclipse.org-planning-council@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
>
> IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.



-- 
Alexander Kurtakov
Red Hat Eclipse Team


Back to the top