>
> I wouldn't say a non-commmitter can't do a release, it's perfectly doable
> but he will need to have some help from a committer on things like
> creating tags and/or publishing the release. In the past I have done a
> release without being a comitter, it was much harder process, but was
> doab
e consumption, and JAR file distribution has been the norm
> for Java-based pacakges for ages, I wonder if it's worth revisiting
> this policy.
>
> -Joan
> - Original Message -
> From: "Nandish Jayaram"
> To: dev@community.apache.org
> Sent: Wednesday, 1
Hi All,
The Apache MADlib team is working on creating CI pipelines, and we
wanted to know if there are any Apache mandates for where the release
artifacts must be built?
We have a CI pipeline which builds the rpm on a docker container. Can
this rpm be released as is, or should we only release art
Hi All,
Apache MADlib made its first TLP release yesterday
(v1.12). During the release process, we had to move
the artifacts from dev/RC folder to the release folder
in the distribution repo. I received an email saying I
must update the release date and version in the Apache
reporter database at:
