On Thu, Aug 29, 2013 at 6:55 AM, Christopher Sean Morrison
<[email protected]>wrote:
>
> On Aug 29, 2013, at 6:38 AM, Tom Browder wrote:
>
> On Wed, Aug 28, 2013 at 10:06 PM, Christopher Sean Morrison <
> [email protected]> wrote:
>
>> Tom,
>>
>> Also, note that public API changes like the one below would have to
>> follow the change policy described in the CHANGES file. My gut says that
>> it'd probably be a minimally impacting
>
>
> I wasn't worried about it because it's new and on the trunk. Does that
> mean that new public API stuff on the trunk can never change after it's
> introduced and before a release prep call? I guess I should be a bit more
> conservative with such things, but this seemed okay since it won't truly be
> used for a while.
>
>
> The API can and does certainly change (per CHANGES, it happens a lot). New
> functions are also okay to add. The commit changed an existing public API
> function to change an argument type (replacing the char * with an enum).
>
Sean, I just added that function to the trunk in the last week. Does that
count as a public release?
-Tom
------------------------------------------------------------------------------
Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
Discover the easy way to master current and previous Microsoft technologies
and advance your career. Get an incredible 1,500+ hours of step-by-step
tutorial videos with LearnDevNow. Subscribe today and save!
http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
