Re: [m2e-dev] m2e 1.4 M7 build (1.4.0.20130508-0158)

[Roberto Sanchez Herrera/Mexico/IBM <rsanchez@xxxxxxxxxxx>]

Thank you, I now see some tags, including
the one for the 1.4 M7 Build., 

Roberto Sanchez Herrera

From:	Igor Fedorenko <igor@xxxxxxxxxxxxxx>
To:	m2e-dev@xxxxxxxxxxx
Date:	08-05-13 20:39
Subject:	Re: [m2e-dev] m2e 1.4 M7 build (1.4.0.20130508-0158)
Sent by:	m2e-dev-bounces@xxxxxxxxxxx

---

I am actually not sure why tags were present. I just
pushed tags from my
local clone, so you should see some of them now. Generally we try to
follow the process described in [1], i.e. tags are pushed shortly after
corresponding builds become available.

[1] http://wiki.eclipse.org/M2E_updatesite_and_gittags

--
Regards,
Igor



On 2013-05-08 5:19 PM, Roberto Sanchez Herrera/Mexico/IBM wrote:
> Hello,
> General question: do milestone builds get tagged? I see in the m2e-core
> repository some tags like milestone/1.1/1.1.0.20111210-1509. But all
the
> milestone tags  are for 1.0 and 1.1. I believe these tags are
really
> useful in case you need to go back and review the code that was shipped
> in a specific milestone
>
> Why was this practice abandoned for 1.1 and newer?
>
> Thanks
>
> Roberto Sanchez Herrera
>
>
>
>
> From:                
 Igor Fedorenko <igor@xxxxxxxxxxxxxx>
> To:                
 Maven Integration for Eclipse developers mailing list
> <m2e-dev@xxxxxxxxxxx>, Maven Integration for Eclipse users mailing
list
> <m2e-users@xxxxxxxxxxx>
> Date:                
 07-05-13 21:27
> Subject:              
   [m2e-dev] m2e 1.4 M7 build (1.4.0.20130508-0158)
> Sent by:              
   m2e-dev-bounces@xxxxxxxxxxx
>
>
> ------------------------------------------------------------------------
>
>
>
> I just published m2e 1.4M7 build (full version 1.4.0.20130508-0158).
> This milestone contains primarily bugfixes and performance improvements
> and you can find full list of changes in [1].
>
> Installation instructions are available on m2e download page [2].
>
> As a reminder, Eclipse Kepler is entering release candidate phase,
with
> RC1 scheduled in just couple weeks [3]. Now is your final opportunity
to
> test that m2e 1.4 works for your projects and to report any problems
and
> regressions. As usual, this can be done either on m2e user or dev
> mailing lists or on bugzilla.
>
> [1]
> https://bugs.eclipse.org/bugs/buglist.cgi?list_id=5409288&query_based_on=m2e%201.4M7&query_format=advanced&target_milestone=Kepler%20M7&product=m2e&known_name=m2e%201.4M7
> [2] http://www.eclipse.org/m2e/download/
> [3] http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan
>
> --
> m2e team
> _______________________________________________
> 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