with release of Foreman 1.3 my work is done and we need a volunteer for
1.4 version. I will be working on 1.3.1 and other minor versions, but it
is good time to start with some planning.
I would like to take the opportunity to thank my mentor Dominic. I will
do my best to be on par as a new mentor for our volunteer.
Indeed, I guess we'll be starting the release process again in a month
or so, per the quarterly cycle.
I'm going to try and do a bit more to reduce the workload at release
time by writing up release notes at the end of, or during sprints, and
doing stable cherry-picking as commits are merged to develop and issues
are assigned to releases.
I'd say we should also nominate somebody to ensure the installer's
tested and modules are up to date, as that can be a bit of work.
We should see if we can identify other areas where the release nanny can
get others to do the low level work and allow them to oversee the
process and check the results.
···
On 05/11/13 10:44, Lukas Zapletal wrote:
> Hello,
>
> with release of Foreman 1.3 my work is done and we need a volunteer for
> 1.4 version. I will be working on 1.3.1 and other minor versions, but it
> is good time to start with some planning.
···
On Tue, Nov 05, 2013 at 11:19:43AM +0000, Dominic Cleal wrote:
> On 05/11/13 10:44, Lukas Zapletal wrote:
> > Hello,
> >
> > with release of Foreman 1.3 my work is done and we need a volunteer for
> > 1.4 version. I will be working on 1.3.1 and other minor versions, but it
> > is good time to start with some planning.
>
> Indeed, I guess we'll be starting the release process again in a month
> or so, per the quarterly cycle.
>
> I'm going to try and do a bit more to reduce the workload at release
> time by writing up release notes at the end of, or during sprints, and
> doing stable cherry-picking as commits are merged to develop and issues
> are assigned to releases.
>
> I'd say we should also nominate somebody to ensure the installer's
> tested and modules are up to date, as that can be a bit of work.
>
> We should see if we can identify other areas where the release nanny can
> get others to do the low level work and allow them to oversee the
> process and check the results.
>
> --
> Dominic Cleal
> Red Hat Engineering
>
> --
> You received this message because you are subscribed to the Google Groups "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
···
On Tuesday, November 12, 2013 4:05:08 AM UTC-5, Lukas Zapletal wrote:
LZ
On Tue, Nov 05, 2013 at 11:19:43AM +0000, Dominic Cleal wrote:
On 05/11/13 10:44, Lukas Zapletal wrote:
Hello,
with release of Foreman 1.3 my work is done and we need a volunteer
for
1.4 version. I will be working on 1.3.1 and other minor versions, but
it
is good time to start with some planning.
Indeed, I guess we’ll be starting the release process again in a month
or so, per the quarterly cycle.
I’m going to try and do a bit more to reduce the workload at release
time by writing up release notes at the end of, or during sprints, and
doing stable cherry-picking as commits are merged to develop and issues
are assigned to releases.
I’d say we should also nominate somebody to ensure the installer’s
tested and modules are up to date, as that can be a bit of work.
We should see if we can identify other areas where the release nanny can
get others to do the low level work and allow them to oversee the
process and check the results.
–
Dominic Cleal
Red Hat Engineering
–
You received this message because you are subscribed to the Google
Groups “foreman-dev” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to foreman-dev...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.