Cos, I tried to give you admin rights, but you already have them.
1.4 released.
All non-closed issues with fix version < 1.8 moved to 1.8.
Pavel.
On Wed, Aug 10, 2016 at 10:27 PM, Konstantin Boudnik wrote:
> BTW, I see another issue with not pruning the tickets _before_ the release
> is
> made
BTW, I see another issue with not pruning the tickets _before_ the release is
made. Right now, there's a bunch of tickets still marked to be fixed in say
1.6, which should've been moved to 1.7 at the time of 1.6 being released.
Also, 1.4 release is still marked as active in JIRA. Unfortunately, I
Great! Thanks for updating the page! I've noticed that we are still using
unsecure md5 and sha1, but i guess this is a topic for a different time ;)
Cheers,
Cos
On Wed, Aug 10, 2016 at 12:26PM, Pavel Tupitsyn wrote:
> Cos, you are right.
>
> More than 300 (!) tickets has been moved to 1.8 yest
Cos, you are right.
More than 300 (!) tickets has been moved to 1.8 yesterday when I released
1.7 version in JIRA.
For what it's worth, I've added a step to vote verification:
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
Pavel
On Tue, Aug 9, 2016 at 9:37 PM, Konstantin Bou
Gents,
this has triggered the recollection of the release notes conversation we had
the other day. Looks like the ticket queue isn't getting pruned in time of the
release, so the changes like that are happening postfactum. This is either
leads to more load on the RM, or might be error-prone.
I w
