Please refrain from FUDding. The solution is to simply update the constants.
Just need to add 4.4 and 10.0 to the constants.
On Tue, Oct 13, 2015 at 10:35 AM, Rob Stryker <rstryker(a)redhat.com> wrote:
> Honestly, I'd just like to say I think it's really strange that 3 weeks
> after freeze started, these filters were still empty. This means that
> people who wanted to work on 4.4.0 once freeze started because they had
> finished all 3.3.0.Final issues has sat for 3 weeks with an empty dashboard.
>
> And yeah, I know it's not a critical issue in the strict sense of the word,
> but this definitely needs to be added to the release process checklist
> somehow. It's been a full week since release.
>
>
> On 10/13/2015 09:45 AM, Nick Boldt wrote:
>>
>
Just need to add 4.4 and 10.0 to the constants.
>>
>
>>
>> Max, now that this tool's been in use for over a year, should it be
>> moved to a jbosstools-* repo instead of your own personal one?
>>
>> Maybe in jbosstools-build-ci (since related to CI) or devdoc (since
>> needs to be updated annually along with devdoc) ?
>>
>> On Mon, Oct 12, 2015 at 4:16 PM, Rob Stryker <rstryker(a)redhat.com> wrote:
>>>
>>> Back from PTO and noticed my dashboard is completely empty. I have jiras
>>> assigned to me for 4.4.0.Alpha1 and 4.3.1.Final, but the filters are
>>> still empty.
>>>
>>> @Max: got time to investigate?
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>>
>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com