My vote goes for making the docs available and marking them as beta. I looked for a dox tag that would help with that but no luck. Maybe append (BETA) to the page name?
On a side note, where do the core devs go for this info? Or do you just "know"... On Sep 11, 2014 6:52 AM, "Stefan Schmidt" <ste...@datenfreihafen.org> wrote: > Hello. > > Now that we are going to have the docs updated with each release Cedric > pointed out that during the merge of efl some docs are no longer easy to > find (or to be found at all). > > I just pushed some changes that made some ecore sub-parts visible again. > During this exercise I realized that we also don't display any docs for > eolian, eolian_cxx and efl. All three are considered a beta API which > made me wonder if they have been left out on purpose. > > It might be good to list them but mark them as BETA somehow. > > Opinions? > > regards > Stefan Schmidt > > > > ------------------------------------------------------------------------------ > Want excitement? > Manually upgrade your production database. > When you want reliability, choose Perforce > Perforce version control. Predictably reliable. > > http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
