See http://jira.codehaus.org/browse/MRELEASE-875.
You are right about 1.9.1, but I cannot repro whatever else was going on.
On Sun, Sep 14, 2014 at 7:01 AM, Benson Margulies
wrote:
>
>
> On Sun, Sep 14, 2014 at 6:33 AM, Robert Scholte
> wrote:
>
>> Hi Benson,
>>
>> there's actually still one
On Sun, Sep 14, 2014 at 6:33 AM, Robert Scholte
wrote:
> Hi Benson,
>
> there's actually still one thing bothering me (and which also blocked me
> for doing this release):
> How can it be that there's a PR (#17) on SCM when the issue is already
> fixed?
> From other issues I remember that for som
Hi Benson,
there's actually still one thing bothering me (and which also blocked me
for doing this release):
How can it be that there's a PR (#17) on SCM when the issue is already
fixed?
From other issues I remember that for some users upgrading to SCM-1.9.1
did help, though for others it d
Benson,
If this release gets done before ASF-15 is released you might want to
revisit https://issues.apache.org/jira/browse/MPOM-55 and update to
the latest versions.
On Sat, Sep 13, 2014 at 6:51 PM, Benson Margulies wrote:
> All this will do is pick up SCM fixes. Still, that seems too big for 2
On Sat, Sep 13, 2014 at 1:06 PM, Robert Scholte
wrote:
> I agree that this is not a 3.0-release.
> 2.5 was mainly a Git release, and IMHO this release is an additional Git
> bugfix release, so 2.5.1 would be fine for me.
>
If no one else expresses an opinion I'll switch to that before I make the
I agree that this is not a 3.0-release.
2.5 was mainly a Git release, and IMHO this release is an additional Git
bugfix release, so 2.5.1 would be fine for me.
Robert
Op Sat, 13 Sep 2014 18:51:03 +0200 schreef Benson Margulies
:
All this will do is pick up SCM fixes. Still, that seems too
All this will do is pick up SCM fixes. Still, that seems too big for 2.5.1
-- but definitely too small for 3.0. So I'm setting up for 2.6.0. If
someone disagrees I will change it again.
