Git Product home page Git Product logo

Comments (8)

chumer avatar chumer commented on May 18, 2024 3

The new policy includes that every API change must be documented in the change log in prosaic form before getting integrated. Changelog descriptions for older versions where added.

from graal.

jtulach avatar jtulach commented on May 18, 2024

I plan to remove the manually written changelog and replace it by automatically generated one that is included in the documentation. NetBeans is using arch.xml and apichanges.xml for that. I'd rather replace that with annotations processed by an annotation processor. But I need to write that tool first.

from graal.

woess avatar woess commented on May 18, 2024

Manually written, it can give short summary/overview about what happened in a release, without going into too much detail. Feels better than having to dig out announcement emails (which served a similar purpose) from the mailing list archive.

from graal.

jtulach avatar jtulach commented on May 18, 2024

First of all we need to mark all elements in the API with the version they were introduced at. Here is my current diff: TruffleAddSinceTag.diff

It assigns version 0.8 to all elements. I have chosen 0.8 as it is the old version I know; probably nobody cares about older versions anymore and it is relatively easy to find out newer elements and change their version of 0.9, 0.10, 0.11.

I plan to apply the @since tag change tomorrow.

from graal.

eregon avatar eregon commented on May 18, 2024

I agree that a manually-written changelog is much more useful than an automated generated list, maybe @since is overkill here?

from graal.

jtulach avatar jtulach commented on May 18, 2024
  • @since tag is a nice way to find out whether an element is or isn't intended to be public.
    • if we had this check, error #82 wouldn't have to be fixed now
  • @since tag provides well-understood information about origin of particular API element
    • Java core API is using it and people know what it means
    • By looking at latest Javadoc one can understand evolution history of the API

from graal.

jtulach avatar jtulach commented on May 18, 2024

The desirable rule to achieve in the Truffle repository should be: "Every element in the API needs to have Javadoc with @since tag":

  • Obviously having elements in the API without Javadoc is wrong
  • with Javadoc being there, the additional requirement to add one more line @since X.Y seems easy

from graal.

jtulach avatar jtulach commented on May 18, 2024

I have added prosaic description of what happened on 0.13 version into the https://github.com/graalvm/truffle/blob/truffle-0.13/CHANGELOG.md based on the sigtest and @SInCE tag information.

from graal.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.