On Tue, Jan 29, 2019 at 9:01 PM Ben Cotton wrote:
> Hi all,
>
> Here's a draft of the F31 QA schedule with your feedback incorporated:
>
> https://fedorapeople.org/groups/schedule/f-31/f-31-quality-tasks.html
>
> Please review it and let me know if anything looks amiss. You can
> reply to this em
Hi all,
Here's a draft of the F31 QA schedule with your feedback incorporated:
https://fedorapeople.org/groups/schedule/f-31/f-31-quality-tasks.html
Please review it and let me know if anything looks amiss. You can
reply to this email or add a comment to the Pagure ticket at:
https://pagure.io/
On Mon, Jan 14, 2019 at 8:32 PM Ben Cotton wrote:
> On Mon, Jan 14, 2019 at 12:45 AM Sumantro Mukherjee
> wrote:
>
> > Usually 2-3 weeks after the GA, we tend to go ahead and call for test
> days
> > which is an email going out to all the teams and subteams notfing that
> we will
> > are accepti
On Mon, Jan 14, 2019 at 12:45 AM Sumantro Mukherjee wrote:
> Usually 2-3 weeks after the GA, we tend to go ahead and call for test days
> which is an email going out to all the teams and subteams notfing that we will
> are accepting test day tickets for the upcoming release cycle.
> We do have so
On Sat, Jan 12, 2019 at 1:14 AM Ben Cotton wrote:
> On Fri, Jan 11, 2019 at 12:43 PM Adam Williamson
> wrote:
>
> > It would be useful to have the branch date / Bodhi activation point on
> > the QA calendar, as that's an important date for us. It would similarly
> > also be useful to have the Ch
On Fri, Jan 11, 2019 at 12:43 PM Adam Williamson
wrote:
> It would be useful to have the branch date / Bodhi activation point on
> the QA calendar, as that's an important date for us. It would similarly
> also be useful to have the Change deadlines on there.
>
That's an easy change. I'll add the
On Fri, 2019-01-11 at 10:58 -0500, Ben Cotton wrote:
> I am beginning to prepare the schedule for Fedora 31. One thing I want
> to do is to make sure it still accurately reflects the work of
> different teams within Fedora. Please look at the tasks on your team's
> schedule [1] and discuss them in
I am beginning to prepare the schedule for Fedora 31. One thing I want
to do is to make sure it still accurately reflects the work of
different teams within Fedora. Please look at the tasks on your team's
schedule [1] and discuss them in your team. Let me know if there are
tasks that should be adde
