[MidoNet] [MidoNet-dev] Version string in midonet/midonet

Guillermo Ontañón guillermo at midokura.com
Fri Aug 7 08:07:17 UTC 2015


Hi guys,

I raised this in the CR:

https://review.gerrithub.io/#/c/241008/

Yes, the epoch should be bumped. IIRC there were mixed opinions and
Galo abandoned his CR. Not sure about the background for the change
that was actually merged.

Regards,
G



On Fri, Aug 7, 2015 at 5:33 AM, Jan Hilberath <jan at midokura.com> wrote:
>> I'd like to wait for midonet repo maintainers' opinions and actions.
>
> Right thing to do.
>
> I'm re-adding the <midonet-dev> list, that got lost on my first reply.
>
> Jan
>
>
>
> On 08/07/2015 11:38 AM, Tomoe Sugihara wrote:
>
> On Fri, Aug 7, 2015 at 9:52 AM, Jan Hilberath <jan at midokura.com> wrote:
>>
>> Hi Tomoe,
>>
>> Let's get it right and do not even think about force upgrading. We have to
>> bump the epoch.
>
>
> +1 from me.
>
>>
>>
>> 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?
>
>
> +1 for being consistent across all the packages.
>
> I'd like to wait for midonet repo maintainers' opinions and actions.
>
> -Tomoe
>
>>
>>
>>
>> Jan
>>
>>
>>
>> On 08/07/2015 09:24 AM, Tomoe Sugihara wrote:
>>
>> Hi list,
>>
>> I noticed that this change was introduced to bump up the version string to
>> 5.0.0-SNAPSHOT.
>> 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.
>>
>> I can think of the following for addressing this issue:
>>
>>  a. bump up epoch number in packaging, or
>>  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.
>>
>> Thanks,
>> Tomoe
>>
>>
>> On Wed, Jul 29, 2015 at 11:38 PM, Dan Mihai Dumitriu <dan at midokura.com>
>> wrote:
>>>
>>> The release plugin helps tremendously to reduce errors and simplify the
>>> process. I really think we should be using it.
>>>
>>> On Wed, Jul 29, 2015 at 11:19 PM, Galo Navarro <galo at midokura.com> wrote:
>>>>
>>>> Hi Dan,
>>>>
>>>> Releases are not done automatically. The process involves a bunch of
>>>> manual steps, one of which is branching and updating the version. As I
>>>> noted in my previous email, AFAIK this step was documented but as JF
>>>> and Jorju are managing that nowadays, and the wiki was recently
>>>> migrated, I can't tell exactly where the current doc lives. In any
>>>> case, the expectations are specced in the wiki [1].
>>>>
>>>> I agree that the gradle plugin could simplify things by automating
>>>> some steps. But in any case the fundamental problem for me is not
>>>> which tool is used to edit the file, but the fact that releases as a
>>>> whole are manual (and thus vulnerable to many errors and ommisions,
>>>> including this one).
>>>>
>>>> [1]: https://github.com/midonet/midonet/wiki/Branching-Model
>>>>
>>>> g
>>>>
>>>> On 29 July 2015 at 15:56, Dan Mihai Dumitriu <dan at midokura.com> wrote:
>>>> > Why isn't updating that master snapshot version automatically done as
>>>> > part
>>>> > of the release process. The maven release plugin can do that, and
>>>> > there are
>>>> > ways to do it in gradle as well.
>>>> >
>>>> > http://www.slideshare.net/evgenyg/release-it
>>>> >
>>>> > https://github.com/researchgate/gradle-release
>>>> >
>>>> >
>>>> > On Jul 22, 2015 8:47 AM, "Galo Navarro" <galo at midokura.com> wrote:
>>>> >>
>>>> >> Fix here: https://review.gerrithub.io/#/c/241008/
>>>> >>
>>>> >> Thanks for the heads up Tomoe.
>>>> >>
>>>> >> @Jf @Jorju is this step added to the release procedures?
>>>> >>
>>>> >> Cheers,
>>>> >> g
>>>> >>
>>>> >> On 22 July 2015 at 06:45, Tomoe Sugihara <tomoe at midokura.com> wrote:
>>>> >> > (x-positing to midonet@ as it affects package versions)
>>>> >> >
>>>> >> > Hi,
>>>> >> >
>>>> >> > I found that the version string on the master
>>>> >> > branch(2015.05-SNAPSHOT)
>>>> >> > is
>>>> >> > older than the latest released version(2015.06).
>>>> >> >
>>>> >> > Shouldn't master version be updated to SNAPSHOT of the next release
>>>> >> > version?
>>>> >> >
>>>> >> > Thanks,
>>>> >> > Tomoe
>>>> >> >
>>>> >> > _______________________________________________
>>>> >> > MidoNet mailing list
>>>> >> > MidoNet at lists.midonet.org
>>>> >> > http://lists.midonet.org/listinfo/midonet
>>>> >> >
>>>> >> _______________________________________________
>>>> >> MidoNet-dev mailing list
>>>> >> MidoNet-dev at lists.midonet.org
>>>> >> http://lists.midonet.org/listinfo/midonet-dev
>>>
>>>
>>
>>
>>
>> _______________________________________________
>> MidoNet mailing list
>> MidoNet at lists.midonet.org
>> http://lists.midonet.org/listinfo/midonet
>>
>>
>>
>> _______________________________________________
>> MidoNet mailing list
>> MidoNet at lists.midonet.org
>> http://lists.midonet.org/listinfo/midonet
>>
>
>
>
> _______________________________________________
> MidoNet mailing list
> MidoNet at lists.midonet.org
> http://lists.midonet.org/listinfo/midonet
>


More information about the MidoNet mailing list