Forgive the dumb question, but if we do...
* TP freeze on the last Wed of the sprint,
* code freeze on the last Thurs of the sprint,
* stage a build to QE on the last Friday of the sprint...
then would this "go/no-go meeting" happen on the last Monday of the sprint,
so that we can release from staging -> production on the last Tuesday of
the sprint?
And isn't that the purpose of the mojo doc [1] & email [2] you produce
confirming that the build is ready to be released? Do we really need
ANOTHER meeting when a single email w/ link to mojo doc has worked for the
last bunch of releases?
[1]
Cheers,
Nick
On Mon, Jul 11, 2016 at 5:32 PM, Alexey Kazakov <alkazako(a)redhat.com> wrote:
It's not only for JBoss Tools but for entire group 2 (code) of
the
devtools team. It includes Eclipse DTS and others.
This event is in devtools calendar and publicly available but I can add
you to the event if you want.
Thanks.
On 07/11/2016 03:29 PM, George Gastaldi wrote:
Are component leads also required to attend the event? I don't see it in
my calendar.
*George Gastaldi*
https://onename.com/gastaldi
On Mon, Jul 11, 2016 at 4:27 PM, Alexey Kazakov <alkazako(a)redhat.com>
wrote:
> I added your to the google event.
>
> On 07/11/2016 03:24 PM, Leonard Dimaggio wrote:
>
> I volunteer! (Just not when I am on PTO. ;-)
>
> -- Len
>
> On Mon, Jul 11, 2016 at 3:15 PM, Alexey Kazakov < <alkazako(a)redhat.com>
> alkazako(a)redhat.com> wrote:
>
>> Yes we can try to combine it with the retrospective. But we will need
>> someone from QE to present on the retrospective then ;)
>>
>>
>> On 07/11/2016 03:04 PM, Leonard Dimaggio wrote:
>>
>> Hi Alexey,
>>
>> It wasn't possible to do this due to all the holidays and PTO last week,
>> but for future sprints (starting with 117), will we have a pre-release
>> review? It's not really a go/no-go meeting as the default is "go" -
but it
>> would be good to have a sprint wrap-up review. Maybe we can combine this
>> with the retrospective?
>>
>> Thanks!,
>> Len
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Fri, Jul 8, 2016 at 2:43 PM, Alexey Kazakov < <alkazako(a)redhat.com>
>> alkazako(a)redhat.com> wrote:
>>
>>> Hi all,
>>>
>>> Just a reminder that our initial plan was to release milestones of JBoss
>>> Tools after every sprint and work on automation of this process so it
>>> doesn't require a lot of efforts any manual work.
>>> But because of holidays in Canada, USA and Czech Republic plus busy Red
>>> Hat Summit week before that we skipped public release of JBoss Tools
>>> 4.4.1.AM1.
>>> Our next (4.4.1.AM2) release will be on July 26 (Tuesday) with
>>> codefreeze on July 21 (Thursday). This will be our first public
>>> milestone release for JBT 4.4.1.
>>> The release schedule is available here -
>>>
>>>
https://issues.jboss.org/projects/JBIDE?selectedItem=com.atlassian.jira.j...
>>>
>>> Thank you.
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>
>>
>>
>> --
>> Len DiMaggio ( <ldimaggi@redhat.com>ldimaggi(a)redhat.com)
>> JBoss by Red Hat
>> 314 Littleton Road
>> Westford, MA 01886 USA
>> tel: 978.392.3179
>> cell: 781.472.9912
>>
http://www.redhat.com
>>
http://community.jboss.org/people/ldimaggio
>>
>>
>>
>>
>
>
> --
> Len DiMaggio ( <ldimaggi@redhat.com>ldimaggi(a)redhat.com)
> JBoss by Red Hat
> 314 Littleton Road
> Westford, MA 01886 USA
> tel: 978.392.3179
> cell: 781.472.9912
>
http://www.redhat.com
>
http://community.jboss.org/people/ldimaggio
>
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
_______________________________________________
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