trafodion-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gunnar Tapper <tapper.gun...@gmail.com>
Subject Re: [RELEASE-PLANNING] Documentation
Date Wed, 30 Nov 2016 20:52:10 GMT
Great! Are you handling to_char(), too?

My plan is to create a Release Management on the wiki so that we can keep
track of tasks and who's doing what for the release, RCs, and then the
checklist for the finalized release.

On Wed, Nov 30, 2016 at 10:51 AM, Dave Birdsall <dave.birdsall@esgyn.com>
wrote:

> Hi Gunnar,
>
> I'll take care of documenting to_date. See JIRA TRAFODION-2285.
>
> Also, in my copious spare time, I have been doing piecemeal updates to the
> Messages Guide. I'm tracking that work in JIRA TRAFODION-2283. If anyone
> would like to help, I invite you to create subtasks under that JIRA so that
> this work is tracked in a more centralized way.
>
> Dave
>
> -----Original Message-----
> From: Gunnar Tapper [mailto:tapper.gunnar@gmail.com]
> Sent: Wednesday, November 30, 2016 9:34 AM
> To: dev@trafodion.incubator.apache.org
> Subject: [RELEASE-PLANNING] Documentation
>
> Hi,
>
> We'll start working on packaging up the next release soon. I'd like to
> update the documentation before we create the release and need your help.
>
> Specifically, I need pointers to developer-level documentation that can be
> moved into the documents. For example, it'd be great to document the
> to_date() function but I'm not going to reverse engineer the code to do so.
>
> I assume that the developer-level documentation is in a Jira or that you
> can send out an e-mail describing what to add to a manual. Please send that
> information to the dev list and I'll consolidate the information.
>
> Do not send "we need to document to_date()" or something like. I need the
> actual information, not a line item.
>
> --
> Thanks,
>
> Gunnar
> *If you think you can you can, if you think you can't you're right.*
>



-- 
Thanks,

Gunnar
*If you think you can you can, if you think you can't you're right.*

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