On 10 July 2012 23:50, Barrie Treloar wrote:
> On Wed, Jul 11, 2012 at 5:33 AM, Anders Hammar wrote:
> > There is currently voting taking place for m-enforcer-p v1.1.1.
> > Earlier there was voting for v1.2, but it was cancelled and the
> > version changed to 1.1.1.
>
> Yes, so Tony can get his
On Wed, Jul 11, 2012 at 5:33 AM, Anders Hammar wrote:
> There is currently voting taking place for m-enforcer-p v1.1.1.
> Earlier there was voting for v1.2, but it was cancelled and the
> version changed to 1.1.1.
Yes, so Tony can get his first binding +1 vote.
I need more, more, more I tells ya!
On Wed, Jul 11, 2012 at 5:33 AM, Anders Hammar wrote:
>>> In JIRA there is version 1.2, 1.4 released (with no issues inside), but the
>>> plugin is
I think a 1.4 being released is a stuff up somewhere.
Brian might know more about it.
If the release has no issues in it, it would be safe to delete
There is currently voting taking place for m-enforcer-p v1.1.1.
Earlier there was voting for v1.2, but it was cancelled and the
version changed to 1.1.1.
/Anders
On Tue, Jul 10, 2012 at 7:42 PM, wrote:
> On Tue, 10 Jul 2012 15:52:20 +0200
> tche...@apache.org wrote:
>
>> Hi,
>>
>> I think there
On Tue, 10 Jul 2012 15:52:20 +0200
tche...@apache.org wrote:
> Hi,
>
> I think there is a little problem with versions of the m-enforcer-p.
>
> In JIRA there is version 1.2, 1.4 released (with no issues inside), but the
> plugin is actually in version 1.1-SNAPSHOT ?
>
> What's the catch ? (if
Hi,
I think there is a little problem with versions of the m-enforcer-p.
In JIRA there is version 1.2, 1.4 released (with no issues inside), but the
plugin is actually in version 1.1-SNAPSHOT ?
What's the catch ? (if any :).
Should we remove version 1.2 and 1.4 and just create a version 1.1.
