Comments (8)
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.
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.
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.
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.
I agree that a manually-written changelog is much more useful than an automated generated list, maybe @since
is overkill here?
from graal.
@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.
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.
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)
- Problem java.lang.NoClassDefFoundError: sun/misc/Unsafe
- [GR-52454] Native Image shutdown hooks don't run upon SIGINT HOT 2
- [GR-52453] [jfr] jdk.ContainerConfiguration doesn't set hostTotalMemory correctly
- [GR-52484] [jfr] jdk.PhysicalMemory event doesn't set 'usedSize' HOT 3
- Is there any problem with graalvm checking illegal strings? HOT 2
- [GR-52483] Native Image call graph imprecision HOT 7
- [GR-52515] META-INF/native-image/... files are ignored in some JARs (large, zip64, self-extracting) HOT 6
- Main entry point class 'HelloWorld.java' neither found on... on M2 HOT 5
- [GR-52475] Error with native image for ktfmt - Resource not found: /org/jetbrains/kotlin/cli/jvm/compiler/KotlinCoreEnvironment$Companion.class HOT 1
- Is there anything missing when graalvm-11uses JVM parameters to run java code? HOT 3
- GraalVM crashes with "fatal error: Initial size of CodeCache is too small" HOT 2
- [GR-52473] Serialization of arrays is not supported in Native Image HOT 4
- Classes not getting initialized HOT 1
- Build a spring boot3 project with hibernate-search and lucene backend, throw a 'undefined reference' error HOT 1
- [GR-52560] Size regression from GraalVM CE 23.0 to GraalVM for JDK 21 (CE) for `byte[] for code metadata` HOT 2
- JSON Metadata Versioning, Backwards Compatibility, and Evolution
- [GR-52553] Defining new classes at runtime is not supported HOT 2
- [GR-52591] Warning: Error processing trace entry map(size=5, {(tracer,reflect),(function,getSystemResource),(caller_class,org.apache.logging.log4j.core.util.Loader),(result,true),(args,[null])}): java.lang.NullPointerException HOT 3
- Caused by: java.lang.IllegalArgumentException: Method "list" could not be invoked HOT 14
- [GR-52611] Add the ability to add comments to JSON configuration file entries HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from graal.