<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Tomoe,<br>
    <br>
    Let's get it right and do not even think about force upgrading. We
    have to bump the epoch.<br>
    <br>
    Instead of doing this separately for each package, what about
    bumping it to "2" for all of them to have a clear cut and consistent
    versions?<br>
    <br>
    Jan<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 08/07/2015 09:24 AM, Tomoe Sugihara
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAAMGQ1u7xZngVJURLVx9XnKqvCbjaykWzQx8mEjDGu10AeoJ=w@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hi list, 
        <div><br>
        </div>
        <div>I noticed that <a moz-do-not-send="true"
href="https://github.com/midonet/midonet/commit/b5da87373997abae0900eef4b836b8a2085e3b09">this
            change</a> was introduced to bump up the version string to
          5.0.0-SNAPSHOT.</div>
        <div>And the problem is that the previous packages with version
          string like 2015.05 are evaluated as newer. So, I cannot get
          newer packages from nightly repo unless I specify version
          specifically. <br>
        </div>
        <div><br>
        </div>
        <div>I can think of the following for addressing this issue:</div>
        <div><br>
        </div>
        <div> a. bump up epoch number in packaging, or </div>
        <div> b. make a big announcement to users to say something like
          "force update required to install newer packages", and remove
          packages with previous version scheme in the nightly repo. </div>
        <div><br>
        </div>
        <div>Thanks,</div>
        <div>Tomoe</div>
        <div><br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Wed, Jul 29, 2015 at 11:38 PM, Dan
          Mihai Dumitriu <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:dan@midokura.com" target="_blank">dan@midokura.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="ltr">The release plugin helps tremendously to
              reduce errors and simplify the process. I really think we
              should be using it.</div>
            <div class="HOEnZb">
              <div class="h5">
                <div class="gmail_extra"><br>
                  <div class="gmail_quote">On Wed, Jul 29, 2015 at 11:19
                    PM, Galo Navarro <span dir="ltr"><<a
                        moz-do-not-send="true"
                        href="mailto:galo@midokura.com" target="_blank">galo@midokura.com</a>></span>
                    wrote:<br>
                    <blockquote class="gmail_quote" style="margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
                      Dan,<br>
                      <br>
                      Releases are not done automatically. The process
                      involves a bunch of<br>
                      manual steps, one of which is branching and
                      updating the version. As I<br>
                      noted in my previous email, AFAIK this step was
                      documented but as JF<br>
                      and Jorju are managing that nowadays, and the wiki
                      was recently<br>
                      migrated, I can't tell exactly where the current
                      doc lives. In any<br>
                      case, the expectations are specced in the wiki
                      [1].<br>
                      <br>
                      I agree that the gradle plugin could simplify
                      things by automating<br>
                      some steps. But in any case the fundamental
                      problem for me is not<br>
                      which tool is used to edit the file, but the fact
                      that releases as a<br>
                      whole are manual (and thus vulnerable to many
                      errors and ommisions,<br>
                      including this one).<br>
                      <br>
                      [1]: <a moz-do-not-send="true"
                        href="https://github.com/midonet/midonet/wiki/Branching-Model"
                        rel="noreferrer" target="_blank">https://github.com/midonet/midonet/wiki/Branching-Model</a><br>
                      <br>
                      g<br>
                      <span><br>
                        On 29 July 2015 at 15:56, Dan Mihai Dumitriu
                        <<a moz-do-not-send="true"
                          href="mailto:dan@midokura.com" target="_blank">dan@midokura.com</a>>
                        wrote:<br>
                        > Why isn't updating that master snapshot
                        version automatically done as part<br>
                        > of the release process. The maven release
                        plugin can do that, and there are<br>
                        > ways to do it in gradle as well.<br>
                        ><br>
                        > <a moz-do-not-send="true"
                          href="http://www.slideshare.net/evgenyg/release-it"
                          rel="noreferrer" target="_blank">http://www.slideshare.net/evgenyg/release-it</a><br>
                        ><br>
                      </span>> <a moz-do-not-send="true"
                        href="https://github.com/researchgate/gradle-release"
                        rel="noreferrer" target="_blank">https://github.com/researchgate/gradle-release</a><br>
                      <span>><br>
                        ><br>
                        > On Jul 22, 2015 8:47 AM, "Galo Navarro"
                        <<a moz-do-not-send="true"
                          href="mailto:galo@midokura.com"
                          target="_blank">galo@midokura.com</a>>
                        wrote:<br>
                        >><br>
                        >> Fix here: <a moz-do-not-send="true"
                          href="https://review.gerrithub.io/#/c/241008/"
                          rel="noreferrer" target="_blank">https://review.gerrithub.io/#/c/241008/</a><br>
                        >><br>
                      </span><span>>> Thanks for the heads up
                        Tomoe.<br>
                        >><br>
                        >> @Jf @Jorju is this step added to the
                        release procedures?<br>
                        >><br>
                        >> Cheers,<br>
                        >> g<br>
                        >><br>
                      </span><span>>> On 22 July 2015 at 06:45,
                        Tomoe Sugihara <<a moz-do-not-send="true"
                          href="mailto:tomoe@midokura.com"
                          target="_blank">tomoe@midokura.com</a>>
                        wrote:<br>
                        >> > (x-positing to midonet@ as it
                        affects package versions)<br>
                        >> ><br>
                        >> > Hi,<br>
                        >> ><br>
                        >> > I found that the version string on
                        the master branch(2015.05-SNAPSHOT)<br>
                        >> > is<br>
                        >> > older than the latest released
                        version(2015.06).<br>
                        >> ><br>
                        >> > Shouldn't master version be
                        updated to SNAPSHOT of the next release<br>
                        >> > version?<br>
                        >> ><br>
                        >> > Thanks,<br>
                        >> > Tomoe<br>
                        >> ><br>
                        >> >
                        _______________________________________________<br>
                        >> > MidoNet mailing list<br>
                      </span>>> > <a moz-do-not-send="true"
                        href="mailto:MidoNet@lists.midonet.org"
                        target="_blank">MidoNet@lists.midonet.org</a><br>
                      <span>>> > <a moz-do-not-send="true"
                          href="http://lists.midonet.org/listinfo/midonet"
                          rel="noreferrer" target="_blank">http://lists.midonet.org/listinfo/midonet</a><br>
                        >> ><br>
                        >>
                        _______________________________________________<br>
                        >> MidoNet-dev mailing list<br>
                      </span>>> <a moz-do-not-send="true"
                        href="mailto:MidoNet-dev@lists.midonet.org"
                        target="_blank">MidoNet-dev@lists.midonet.org</a><br>
                      >> <a moz-do-not-send="true"
                        href="http://lists.midonet.org/listinfo/midonet-dev"
                        rel="noreferrer" target="_blank">http://lists.midonet.org/listinfo/midonet-dev</a><br>
                    </blockquote>
                  </div>
                  <br>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
MidoNet mailing list
<a class="moz-txt-link-abbreviated" href="mailto:MidoNet@lists.midonet.org">MidoNet@lists.midonet.org</a>
<a class="moz-txt-link-freetext" href="http://lists.midonet.org/listinfo/midonet">http://lists.midonet.org/listinfo/midonet</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>