falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pavan Kolamuri <pavan.kolam...@inmobi.com>
Subject Re: Falcon site moved to git
Date Tue, 15 Mar 2016 11:55:55 GMT
Yes, restructuring is required and we should have complete docs for each
release and trunk as well.

On Tue, Mar 15, 2016 at 5:18 PM, Sandeep Samudrala <sandysmdl@gmail.com>
wrote:

> The above approach sounds good. End users generally look for what is being
> available in the latest release that is out.
> We can always have upcoming/development section to have for either delta or
> the whole set of changes upon each pull request merge.
>
> On Tue, Mar 15, 2016 at 5:08 PM, Ajay Yadav <ajaynsit@gmail.com> wrote:
>
> > I think we need to change the structure of the site and move most of the
> > documentation under release version links. We should add a link for trunk
> > version as well. Things like Project information, Architecture etc. can
> > stay out of those sections. I also think it is good to have an automated
> > merge to publish docs on the site under the trunk version link. It allows
> > verification of the documentation in smaller chunks and eases the release
> > process.
> >
>



-- 
Thanks and regards
Pavan Kumar Kolamuri

-- 
_____________________________________________________________
The information contained in this communication is intended solely for the 
use of the individual or entity to whom it is addressed and others 
authorized to receive it. It may contain confidential or legally privileged 
information. If you are not the intended recipient you are hereby notified 
that any disclosure, copying, distribution or taking any action in reliance 
on the contents of this information is strictly prohibited and may be 
unlawful. If you have received this communication in error, please notify 
us immediately by responding to this email and then delete it from your 
system. The firm is neither liable for the proper and complete transmission 
of the information contained in this communication nor for any delay in its 
receipt.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message