« Return to Thread: Documentation is generated from the trunk not from the latest stable release
RE: Documentation is generated from the trunk not from the latest stable release
by wllm
::
Rate this Message:
OK, the current policy is to only maintain docs on trunk to make it
easier for doc authors and translators to check in their changes (no
merge required). I'm not a big fan of this policy, to tell you the
truth. We'll probably be changing this soon. Right now I don't have the
change scheduled, and it will require some education so that everyone is
aware that they must merge changes to release branches, when it is
required, and how to do it.
,Wil
> -----Original Message-----
> From: Thomas Weidner [mailto:thomas.weidner@...]
> Sent: Friday, October 10, 2008 2:24 PM
> To: Wil Sinclair; fw-docs@...
> Subject: Re: Documentation is generated from the trunk not from the
> latest stable release
>
> Wil,
>
> what he've mentioned would still not be covered.
> The docu failures he mentioned for I18N were integrated for 1.6 butthe
> dev-team decided to delay them for 1.7.
> So this could still occur in such a case.
>
> The right solution is to have docu also branched.
> As new features are only for trunk this should be no problem.
> This way we could even provide a docu for the subreleases and a docu
> for the
> nightly snapshot the same time.
>
> Greetings
> Thomas Weidner, I18N Team Leader, Zend Framework
> http://www.thomasweidner.com
>
> ----- Original Message -----
> From: "Wil Sinclair" <wil@...>
> To: "Jean-Marc Fontaine" <jmf@...>; <fw-docs@...>
> Sent: Friday, October 10, 2008 9:54 PM
> Subject: RE: Documentation is generated from the trunk not from the
> latest
> stable release
>
>
> We've already discussed how to fix this on the site. What do youpeople
> think would be best? Maybe just making the last production release
> available on the site with a clear statement saying what version they
> are associated with? If someone is working from trunk, it seems to me
> that they will likely also have the doc-fu to build the API docs.
>
> ,Wil
>
> > -----Original Message-----
> > From: Jean-Marc Fontaine [mailto:jmf@...]
> > Sent: Friday, October 10, 2008 12:01 AM
> > To: fw-docs@...
> > Subject: Documentation is generated from the trunk not from the
> latest
> > stable release
> >
> >
> > Documentation on the website is generated from the trunk and notfrom
> > the
> > latest stable release.
> >
> > Thus, newly implemented features appear in the documentation but
they
> > can't
> > be used with the latest stable release. I lost time twice this week
> > because
> > of this.
> >
> > The routing by hostname do not work in 1.6.1 the way it is described
> in
> > the
> > documentation and the "ignore" option of Zend_Translate described in
> > the
> > documentation won't be available before 1.7 release.
> >
> > Regards,
> >
> > Jean-Marc
> > --
> > View this message in context:http://www.nabble.com/Documentation-is-
> > generated-from-the-trunk-not-from-the-latest-stable-release-
> > tp19912997p19912997.html
> > Sent from the Zend Doc mailing list archive at Nabble.com.
easier for doc authors and translators to check in their changes (no
merge required). I'm not a big fan of this policy, to tell you the
truth. We'll probably be changing this soon. Right now I don't have the
change scheduled, and it will require some education so that everyone is
aware that they must merge changes to release branches, when it is
required, and how to do it.
,Wil
> -----Original Message-----
> From: Thomas Weidner [mailto:thomas.weidner@...]
> Sent: Friday, October 10, 2008 2:24 PM
> To: Wil Sinclair; fw-docs@...
> Subject: Re: Documentation is generated from the trunk not from the
> latest stable release
>
> Wil,
>
> what he've mentioned would still not be covered.
> The docu failures he mentioned for I18N were integrated for 1.6 but
> dev-team decided to delay them for 1.7.
> So this could still occur in such a case.
>
> The right solution is to have docu also branched.
> As new features are only for trunk this should be no problem.
> This way we could even provide a docu for the subreleases and a docu
> for the
> nightly snapshot the same time.
>
> Greetings
> Thomas Weidner, I18N Team Leader, Zend Framework
> http://www.thomasweidner.com
>
> ----- Original Message -----
> From: "Wil Sinclair" <wil@...>
> To: "Jean-Marc Fontaine" <jmf@...>; <fw-docs@...>
> Sent: Friday, October 10, 2008 9:54 PM
> Subject: RE: Documentation is generated from the trunk not from the
> latest
> stable release
>
>
> We've already discussed how to fix this on the site. What do you
> think would be best? Maybe just making the last production release
> available on the site with a clear statement saying what version they
> are associated with? If someone is working from trunk, it seems to me
> that they will likely also have the doc-fu to build the API docs.
>
> ,Wil
>
> > -----Original Message-----
> > From: Jean-Marc Fontaine [mailto:jmf@...]
> > Sent: Friday, October 10, 2008 12:01 AM
> > To: fw-docs@...
> > Subject: Documentation is generated from the trunk not from the
> latest
> > stable release
> >
> >
> > Documentation on the website is generated from the trunk and not
> > the
> > latest stable release.
> >
> > Thus, newly implemented features appear in the documentation but
they
> > can't
> > be used with the latest stable release. I lost time twice this week
> > because
> > of this.
> >
> > The routing by hostname do not work in 1.6.1 the way it is described
> in
> > the
> > documentation and the "ignore" option of Zend_Translate described in
> > the
> > documentation won't be available before 1.7 release.
> >
> > Regards,
> >
> > Jean-Marc
> > --
> > View this message in context:
> > generated-from-the-trunk-not-from-the-latest-stable-release-
> > tp19912997p19912997.html
> > Sent from the Zend Doc mailing list archive at Nabble.com.
« Return to Thread: Documentation is generated from the trunk not from the latest stable release
| Free embeddable forum powered by Nabble | Forum Help |
