On Fri, Aug 12, 2016 at 11:23 AM Josh Elser <[email protected]> wrote:

>
>
> Christopher wrote:
> > So, now that the vote on the incubator list passed, I've moved the
> release
> > artifacts to the right area in SVN, for mirroring, and released the Maven
> > repository.
> >
> > I've also cleaned up the old RC branches and staging repos, and merged in
> > the outstanding PR for updating the reference to the parent POM in the
> > master branch's POM.
> >
> > I've created a ticket for updating the website downloads page (
> > https://github.com/apache/incubator-fluo-website/issues/17)
> >
> > Once we update the downloads page and let the mirrors propagate, we can
> do
> > an [ANNOUNCE] thread on this list, but I don't think we need to bother
> > sending to the wider [email protected]. I don't think they're
> significant
> > enough to warrant the broad announcement... especially since they aren't
> > very useful on their own.
> >
> > Are there any other remaining tasks which I have not thought of?
>
> Besides making sure the main repo is updated with those artifacts, nope :).
>
>
By main repo, do you mean svn dist, Maven Central, or git? I think I've
taken care of all 3.
http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.fluo%22
https://www.apache.org/dist/incubator/fluo/
https://github.com/apache/incubator-fluo/commit/7915c5df43fc595e62a4295c1a15ec349ae82a67
https://github.com/apache/incubator-fluo/releases


> Would be nice to make sure Jenkins is now happy.
>
>
I checked and looks fine. I even created a new job for build-resources:
https://builds.apache.org/view/F/view/Fluo/

(BTW, I moved Fluo from the "E-G" group to a newly created "F" group... I
hated the constantly changing URLs in Jenkins jobs, so as Keith worded it,
I "created a split point which can't be [further] split").


> You'll probably get a ping from reporter.a.o to add a release date too.
>

No, that's only for TLPs, to help generate content for committee reports.
Incubator reports are done differently, as you know. I double-checked in
reporter.a.o, and there were no previously added incubator releases, so I
imagine we don't need to either.

However, that does remind me that we need to update our DOAP on the site.

Reply via email to