Suggestion to release a RC1 version of MetaModel 4.4.0

[Kasper Sørensen <i....@gmail.com>]

Hi all,

In our project we've started using some of the improvements made in the
master codebase (4.4.0-SNAPSHOT). As we don't have any released version
that cover the slight interface changes and so on, our builds are not
functioning at the moment and that actually makes it hard to mature the MM
4.4.0-SNAPSHOT codebase.

First of all, are any of you in a similar situation, and how do you
normally mitigate it? Do you do an internal release to a private Maven repo
or something like that sometimes?

Unless there's some great solution that I missed, I would like to propose
to release MetaModel "4.4.0-RC1". The purpose of this release would be to
have a released set of artifacts that can be used by projects and that way
testdrive our proposal for the coming "more finalized" release called
simply "4.4.0".

Best regards,
Kasper

Re: Suggestion to release a RC1 version of MetaModel 4.4.0

[Kasper Sørensen <i....@gmail.com>]

OK I will stage a release then.

2015-08-27 21:48 GMT+02:00 Alberto Rodriguez <ar...@gmail.com>:

> Hi Kasper,
>
> we've run several times into a similar issue when we find a bug in MM and
> we can't wait for a new version to be released. To mitigate it we've got an
> internal repo where we publish our "unofficial" artifacts.
>
> Anyway, I think this is a good opportunity to start working with release
> candidates and test out if our release process is ready for that.
>
> Kind regards,
>
> Alberto
>
> 2015-08-26 9:07 GMT+02:00 Kasper Sørensen <i.am.kasper.sorensen@gmail.com
> >:
>
> > Hi all,
> >
> > In our project we've started using some of the improvements made in the
> > master codebase (4.4.0-SNAPSHOT). As we don't have any released version
> > that cover the slight interface changes and so on, our builds are not
> > functioning at the moment and that actually makes it hard to mature the
> MM
> > 4.4.0-SNAPSHOT codebase.
> >
> > First of all, are any of you in a similar situation, and how do you
> > normally mitigate it? Do you do an internal release to a private Maven
> repo
> > or something like that sometimes?
> >
> > Unless there's some great solution that I missed, I would like to propose
> > to release MetaModel "4.4.0-RC1". The purpose of this release would be to
> > have a released set of artifacts that can be used by projects and that
> way
> > testdrive our proposal for the coming "more finalized" release called
> > simply "4.4.0".
> >
> > Best regards,
> > Kasper
> >
>

Re: Suggestion to release a RC1 version of MetaModel 4.4.0

[Alberto Rodriguez <ar...@gmail.com>]

Hi Kasper,

we've run several times into a similar issue when we find a bug in MM and
we can't wait for a new version to be released. To mitigate it we've got an
internal repo where we publish our "unofficial" artifacts.

Anyway, I think this is a good opportunity to start working with release
candidates and test out if our release process is ready for that.

Kind regards,

Alberto

2015-08-26 9:07 GMT+02:00 Kasper Sørensen <i....@gmail.com>:

> Hi all,
>
> In our project we've started using some of the improvements made in the
> master codebase (4.4.0-SNAPSHOT). As we don't have any released version
> that cover the slight interface changes and so on, our builds are not
> functioning at the moment and that actually makes it hard to mature the MM
> 4.4.0-SNAPSHOT codebase.
>
> First of all, are any of you in a similar situation, and how do you
> normally mitigate it? Do you do an internal release to a private Maven repo
> or something like that sometimes?
>
> Unless there's some great solution that I missed, I would like to propose
> to release MetaModel "4.4.0-RC1". The purpose of this release would be to
> have a released set of artifacts that can be used by projects and that way
> testdrive our proposal for the coming "more finalized" release called
> simply "4.4.0".
>
> Best regards,
> Kasper
>