[work] [Qgis-release-team] Re: Please revise release checklist template

Otto Dassau otto.dassau at gmx.de
Mon Jul 14 11:27:29 EDT 2008


Hi,

On Mon, 14 Jul 2008 16:58:30 +0200
"Tim Sutton" <tim at linfiniti.com> wrote:

> Hi Tara (I'll pitch in here to save Otto the trouble)
> 
> 2008/7/14 Tara Athan <tara_athan at alt2is.com>:
> > Otto- I wasn't on the list for making changes to the Release Checklist, so I
> > assume you are the person responsible for integrating the documentation
> > needs into the checklist (which is fine by me). For v1.0, we requested a few
> > things, (win and mac build, changelog) after the feature freeze.
> 
> You are most welcome to give input - I just passed it onto Otto as I
> had directly put his name next to items. More names can be added and
> the template edited etc. no problem from me. Just bear in mind this is
> the *template* under discussion (see below).

I didn't pay much attention to the integrating of the documentation, because we
are planning for 1.0 and this is 0.11.0. So I just thought of tasks for Werner
for the current release. But I agree, it is a good idea to add things to this
checklist now so we have it ready for 1.0 and it would be great, if you and
anybody else, who is involved and has ideas adds their notes.

> > Could you please tell me - is there a reason that the changelog is delayed
> > one week after feature freeze?
> 
> Yes - because the release team needs time to sift through all the
> commit messages up to the point of feature freeze and distill the
> changes into something human intelligible (to create the changelog).
> 
> >It would be very helpful to the documentation
> > writers to have that changelog rather than having to experiment to figure
> > out what the new features are.
> 
> Understood. I'm not sure how we can resolve this - you can watch the
> changelog wiki page (subscribe to it) and also liase with Richard who
> normally is in place to make sure the changelog gets done.

All in all there are many new features in QGIS since version 0.9 (documentation
status), but there won't be so many from 0.11.0 to 1.0. So I would suggest we
start updating now as much text and examples as possible and then "only" have a
few features and the screenshots left. That should be ok.

I would suggest that the documentation team meets on IRC about that soon, so we
(Tara, Werner, Stephan H. and Otto) can make a concrete plan and set deadlines
for 1.0. If you agree, I will write an email to the community-team list about
that.

> > Also the optional item at three weeks mentions a "build" for bug fixes, and
> > I assume that means a Linux build?
> 
> I put 'optional' because this is the master checklist template that
> gets used for every release. From the checklist template we create a
> new checklist at the start of each release cycle. The  master
> checklist is continually improved as we learn new things each release.
> In some release cycles the (e.g. pure bug fix release) there often
> isn't time for building preview builds. The build assumes all distros
> and operating systems - dependent on who volunteers to make a test
> build. In the case of 1.0.0 release we should try to liase with
> packagers to make sure it happens for this occasion.
> 
> >Can we get win and mac builds at that
> > time also?  If not, then all our documentation writers, myself included,
> > will need to be able to use the Linux build (with msys?), and we should
> > write up and test a procedure for doing that before we get to that point
> > with v1.0.
> 
> See above. I can pretty much guarantee you an ubuntu build (since I
> can do that myself). I think Marco Pasetti will be happy to make you a
> test build for windows. Jef may also be able to help here (but perhaps
> without grass).

that would be great!

  Otto

> > Apparently we can make screenshots anytime after the feature freeze, which
> > will make the process smoother.
> 
> Yes you should be able to make screenshots after the feature freeze.
> If someone absolutely has to change a dialog to fix a bug or whatever
> (it could happen), we will notify you so that you at least know
> something has changed.
> 
> > The timeline gives us 3 weeks to update the English documentation if our
> > goal is to simultaneously release with the software- do you think this is
> > possible?
> 
> It would be great if you all manage to pull that rabbit out of the hat!
>
> Thanks for the great work you are doing as always..!
> 
> Regards
> 
> Tim
> 
> >
> > Tara
> >
> > Otto Dassau wrote:
> >>
> >> On Mon, 14 Jul 2008 10:34:08 +0200
> >> "Tim Sutton" <tim at linfiniti.com> wrote:
> >>
> >>
> >>>
> >>> Hi All
> >>>
> >>> You are receiving this email because somewhere in the release
> >>> checklist process we need your input. I have finished a batch of
> >>> revisions to the template to:
> >>>  - try to make the release process a little clearer to casual
> >>> observers and new release team members
> >>>  - try to make it clear who should be doing what
> >>>  - try to make the timings clearer
> >>>
> >>> http://wiki.qgis.org/qgiswiki/ReleaseChecklistTemplate
> >>>
> >>> I have colour coded many entries in the list and given each of you a
> >>> unique colour. Could I ask you all to give the template a 'once over'
> >>> and see if you are happy where I have assigned items to you. I know in
> >>> some cases (Otto in particular) I have put in peoples names rather
> >>> than their delegated team members. Feel free to change the template /
> >>> your colour etc as needed. Also if you are not happy with the
> >>> allocations I made just let me know and we can rejig the list. If you
> >>> could finalise your changes by tomorrow that will be great as I will
> >>> be generating the checklist for 1.0.0 then.
> >>>
> >>
> >> I added the item below as well as a tasks for the (GUI translation team
> >> lead)
> >> and added Werner as Cc:. I think it belongs together, if it is ok for both
> >> of
> >> you (Werner and Tim).
> >>
> >> regards,
> >>  Otto
> >>
> >>>
> >>> Regards
> >>>
> >>>
> >>>
> >>
> >> _______________________________________________
> >> Qgis-release-team mailing list
> >> Qgis-release-team at lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/qgis-release-team
> >>
> >> No virus found in this incoming message.
> >> Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database:
> >> 270.4.10/1551 - Release Date: 7/14/2008 6:49 AM
> >>
> >>
> >>
> >> No virus found in this incoming message.
> >> Checked by AVG - http://www.avg.com Version: 8.0.138 / Virus Database:
> >> 270.4.10/1551 - Release Date: 7/14/2008 6:49 AM
> >>
> >>
> >>
> >>
> >
> >
> > --
> > My e-mail delivery has been unreliable lately, so I am asking for
> > return receipts from all my email messages.
> > OK'ing the return receipt lets me know that my message was delivered.
> > Thank you.
> >
> > Tara Athan
> > Principal, Alternatives to Invasive Species
> > tara_athan [AT] alt2is.com
> > 707-485-1198
> > PO Box 415
> > Redwood Valley, CA 95470
> >
> > _______________________________________________
> > Qgis-release-team mailing list
> > Qgis-release-team at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/qgis-release-team
> >
> 
> 
> 


More information about the Qgis-release-team mailing list