Agreed, it's also been a little over 3 months, so we're probably about due for another release.
We do have a handful of open pull requests that feel close-ish to being merged--maybe once those are in would be the right time for our first TLP release. On 3/1/21 4:57 PM, Beckerle, Mike wrote: > Thanks Chris, > > Ok, so nothing to do here then. > > My next thought then, is that we need to cut a new release soon, so that we > have the most recent release without any incubator artifacts in it. I'll > raise that separately. > ________________________________ > From: Christofer Dutz <christofer.d...@c-ware.de> > Sent: Monday, March 1, 2021 4:55 PM > To: dev@daffodil.apache.org <dev@daffodil.apache.org> > Subject: AW: Maven Central broken source code links for all versions of > Daffodil > > Hi Mike, > > I hope I didn't mis-understand you, but: > I think nothing has to be changed. The artifacts released before incubation > all have the name "incubator-" or "incubating-" in them. This is not changed > after graduation. The first release you do after graduation will not have > that prefix. Actually removing the "incubating" from the artifacts in maven > central, would lead people to think this was a top-level-release where all > things are expected to be good from a legal point of view, while incubating > releases might not be as perfect. > > Chris > > Von: Beckerle, Mike <mbecke...@owlcyberdefense.com> > Gesendet: Montag, 1. März 2021 22:41 > An: dev@daffodil.apache.org > Betreff: Maven Central broken source code links for all versions of Daffodil > > So since we are now a TLP, URLs like those on Maven Central that say where > our source is, they're all broken now, since our repository no longer has > "incubator-" in its name. (e.g., > https://gitbox.apache.org/repos/asf/incubator-daffodil.git is used on Maven > central for our 3.0.0 artifacts, and all prior releases have the same issue.) > > I checked with INFRA, and they don't normally fix this by forwarding those > URLs. (https://issues.apache.org/jira/browse/INFRA-21438) > > Does anyone know if this aspect of the Maven Central database can be somehow > updated without having to re-release everything? > > The broken link seems to come out of the XML description of the artifact. I > assume this artifact is generated from our release process. > > Mike Beckerle | Principal Engineer > > [cid:557ed22c-e5b0-4d68-94ea-91e775d4ebf4] > > mbecke...@owlcyberdefense.com<mailto:bhum...@owlcyberdefense.com> > P +1-781-330-0412 > > Connect with us! > > [cid:003c8262-2d35-4076-a3e4-7fe5609caaa4]<https://www.linkedin.com/company/owlcyberdefense/>[cid:859563ee-7bd9-4490-a2c9-c4f90fd85d8b]<https://twitter.com/owlcyberdefense> > > [cid:e87a88f8-bd26-4362-900b-6c19bada69e5]<https://owlcyberdefense.com/resources/events/> > > > > The information contained in this transmission is for the personal and > confidential use of the individual or entity to which it is addressed. If the > reader is not the intended recipient, you are hereby notified that any > review, dissemination, or copying of this communication is strictly > prohibited. If you have received this transmission in error, please notify > the sender immediately >
