<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 16, 2014 at 12:50 PM, Bruno Oliveira <span dir="ltr"><<a href="mailto:bruno@abstractj.org" target="_blank">bruno@abstractj.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On 2014-10-16, Daniel Passos wrote:<br>
> Hi Matthias,<br>
><br>
> Of course, not sure if it's the correct but in my flow I only push it to<br>
> repo, after release it, so, we can revert it or add something like this[1]<br>
> without dirtying the repository<br>
><br>
> I have 2 questions<br>
><br>
> 1) Should I push it when I stage a version?<br>
<br>
</span>I don't think so. Part of our release process is: push the tag first,<br>
stage and after release, push the changes -<br>
<a href="https://github.com/aerogear/collateral/wiki/Release-Process-(Java)" target="_blank">https://github.com/aerogear/collateral/wiki/Release-Process-(Java)</a></blockquote><div><br></div><div>yeah, there is this recommendation: </div><div><br></div><div>====</div><div><strong style="color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,'Segoe UI',Arial,freesans,sans-serif;font-size:16px;line-height:25.6000003814697px">Note 2:</strong><span style="color:rgb(51,51,51);font-family:'Helvetica Neue',Helvetica,'Segoe UI',Arial,freesans,sans-serif;font-size:16px;line-height:25.6000003814697px"> You only want to do this once your staging time has ended and tests have been successful.</span><br></div><div>====<br></div><div><br></div><div>In the past I pushed the version update to master, before staging, after the "mvn release:perform" has been executed successful.</div><div><br></div><div>But yeah, in case something would have gone wrong, during the stating period, I'd have needed to revert that :) </div><div><br></div><div>I think the current process, with the above recommendation, works well for us</div><div><br></div><div>-M</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br>
<br>
It make the process easy to revert changes, if something goes wrong you<br>
just need to cancel the release and delete the tag.<br>
<span class=""><br>
><br>
> 2) Should I add this[1] in 0.2.8 version?<br>
><br>
> [1] <a href="https://github.com/aerogear/aerogear-parent/pull/28" target="_blank">https://github.com/aerogear/aerogear-parent/pull/28</a><br>
<br>
</span>I think this is pretty much coordinated with the team, once you start<br>
the release process, no more changes should be added until we release<br>
and push the commits related to it.<br>
<span class=""><br>
><br>
> -- Passos<br>
><br>
><br>
> On Thu, Oct 16, 2014 at 4:52 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>><br>
> wrote:<br>
><br>
> > looks like the pom on the actual git repo is still 0.2.8-SNAPSHOT, but we<br>
> > do have a 0.2.8 tag<br>
> > <a href="https://github.com/aerogear/aerogear-parent/blob/master/pom.xml" target="_blank">https://github.com/aerogear/aerogear-parent/blob/master/pom.xml</a><br>
> ><br>
> > Noticed when I wanted to merge<br>
> > <a href="https://github.com/aerogear/aerogear-parent/pull/28" target="_blank">https://github.com/aerogear/aerogear-parent/pull/28</a><br>
> ><br>
> > You mind pushing the master changes, from the release plugin ?<br>
> ><br>
> ><br>
> ><br>
> > On Tue, Oct 14, 2014 at 4:36 PM, Daniel Passos <<a href="mailto:daniel@passos.me">daniel@passos.me</a>> wrote:<br>
> ><br>
> >> Hi,<br>
> >><br>
> >> I’d like to run a new release of our parent/bom.<br>
> >><br>
> >> Here is some changes related to newer versions:<br>
> >><br>
</span>> >> - AEROGEAR-1526 - Update Android Support library version<br>
> >> <<a href="https://issues.jboss.org/browse/AEROGEAR-1526" target="_blank">https://issues.jboss.org/browse/AEROGEAR-1526</a>><br>
> >> - AEROGEAR-1525 - Remove unnecessary dependencies<br>
> >> <<a href="https://issues.jboss.org/browse/AEROGEAR-1525" target="_blank">https://issues.jboss.org/browse/AEROGEAR-1525</a>><br>
> >> - AEROGEAR-1524 - Change Android Maven Central stub to real Android<br>
<span class="">> >> library from Maven SDK deploy<br>
</span>> >> <<a href="https://issues.jboss.org/browse/AEROGEAR-1524" target="_blank">https://issues.jboss.org/browse/AEROGEAR-1524</a>><br>
> >> - AEROGEAR-1527 - Move gcm server and json simple from android bom to<br>
> >> bom <<a href="https://issues.jboss.org/browse/AEROGEAR-1527" target="_blank">https://issues.jboss.org/browse/AEROGEAR-1527</a>><br>
<span class="">> >><br>
> >> Feel free to test it. I have plan to release it next thursday.<br>
> >><br>
> >> The staging repo is here:<br>
> >><br>
> >> <a href="https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4026/" target="_blank">https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-4026/</a><br>
> >><br>
> >> — Passos<br>
> >><br>
> ><br>
<br>
</span><span class="">> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
--<br>
<br>
</span>abstractj<br>
PGP: 0x84DC9914<br>
<div class=""><div class="h5">_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>