Hi JB et al.,

No worries, the releases are out so we can now start working towards a
5.0.4 and 5.1.2 that are based on Karaf 2.3.6.  It looks like Jamie is
already making progress on that at the Karaf end.
In the meanwhile, I created those new versions and moved issues that
are not yet bound to be fixed by the Karaf upgrade to the new
5.0.x/5.1.x versions.

Regards,

Gert


On Tue, Jul 22, 2014 at 9:21 PM, Jean-Baptiste Onofré <[email protected]> wrote:
> +1 for both.
>
> It's my bad for the SNAPSHOT: I thought I would have been able to release
> the Karaf releases earlier :/
>
> My apologize.
>
> Regards
> JB
>
>
> On 07/22/2014 12:22 PM, Gert Vanthienen wrote:
>>
>> L.S.,
>>
>>
>> While preparing the 5.0.3 and 5.1.1 releases, I noticed there are two
>> things we could improve to make things a bit easier at release time.
>>
>> My first proposal would be to avoid SNAPSHOT dependencies on the
>> maintenance branches (currently, 5.0.x and 5.1.x). Since we're using
>> git now, we can easily do that kind of work in a topic branch and then
>> merge those changes as soon as the dependency gets released. That way,
>> we can at any time upgrade other dependencies and cut a new
>> maintenance release with whatever dependency version are available at
>> that time.
>>
>> The second proposal would be to introduce dummy versions for those
>> maintenance branches in JIRA, e.g. have a 5.0.x and 5.1.x version
>> there. This morning, in order to create the release notes, I ended up
>> changing versions on a number of issues, just bumping it to
>> 5.0.4/5.1.2 because we were waiting on feedback, a release of an
>> another project, ...
>>
>> Perhaps we could assign the dummy 5.0.x/5.1.x versions for planning
>> what we want to get fixed in some upcoming maintenance release and
>> only put in a real version once we actually have the fix in the branch
>> or have a dependency version available that fixes the issue.
>>
>>
>> Regards,
>>
>> Gert Vanthienen
>>
>
> --
> Jean-Baptiste Onofré
> [email protected]
> http://blog.nanthrax.net
> Talend - http://www.talend.com

Reply via email to