On Mon, Jan 26, 2015 at 4:21 AM, Steve Loughran <[email protected]> wrote:
> On 23 January 2015 at 20:49, Billie Rinaldi <[email protected]> > wrote: > > > -1: > > > > > (sighs) > > > > The release number doesn't have incubating (e.g. 0.61.0-incubating), so > > "incubating" is missing from the artifact file names. I've checked over > > slider-0.61.0-source-release.tar.gz and its contents look okay. One > weird > > thing is it untars to apache-slider-*. This is because we're setting the > > finalName in the pom, but maven doesn't get around to renaming the > tarball > > before deploying it. We could consider not specifying the finalName so > > that the untarred directory matches the tarball name. > > > > I'll do that, so at least they are consistent. > > > > > > > Another issue is that we're releasing binary artifacts now, so we have to > > update their license and notice for the bundled jars. The > > slider-assembly-0.61.0-all.tar.gz tarball is just copying the license > from > > the top level. It doesn't have a notice file. The > > slider-agent-0.61.0.tar.gz tarball has neither license nor notice. The > top > > level license and notice do cover the agent's dependencies, so we could > > just copy those into that artifact if we wanted. > > These tarballs also need disclaimer files. > > > > > OK > > > > The command logger tarball and zip are also missing these files. It > would > > be nice if we could just release slider-core and slider-agent, maybe > > slider-assembly, and not deploy anything else. I could help try to make > > the maven profiles do that, if we want it to work that way. (If we skip > > slider-assembly, we won't even have to make an updated license and notice > > for it ...) > > > > > Sounds good, except I'd like the functional tests JARs published for > downstream use and they depend on the assembly. > > Culling the agent & assembly would imply splitting out slider-funtests from > slider-funtests-command-logger; not a change I want to do in the 0.6 > branch. > OK. I'm not thrilled about releasing the command logger (mainly because the artifact IDs of "command-logger" and "apache-slider-command-logger" in the top-level group ID org.apache.slider are quite confusing), but there's no obstacle if we get their license / notice / disclaimer / etc. set up. > > > > > On Thu, Jan 22, 2015 at 10:20 AM, Steve Loughran <[email protected] > > > > wrote: > > > > > Hello folks, > > > > > > This is a call for a vote on Apache Slider Incubating 0.61.0 release. > > > > > > > > > The issues fixed in this release are listed at at: > > > https://issues.apache.org/jira/browse/SLIDER/fixforversion/12329034 > > > > > > This is the same source as slider 0.60.0, except now it is is being > > > released > > > via a build process which publishes the release candidate artifacts to > > the > > > apache > > > maven staging repository > > > > > > As a result, this s a source+binary release. > > > > > > Thanks to everyone who have contributed to this release! > > > > > > > > > Git source checksum d3fd75007a209cf6439dde99c35a46a2632ca79d > > > > > > tag: > > > > > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;a=tag;h=refs/tags/slider-0.61.0 > > > > > > Staging site: > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapacheslider-1002/org/apache/slider/ > > > > > > The single archive is in > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapacheslider-1002/org/apache/slider/slider-assembly/0.61.0/ > > > > > > PGP release keys (signed as [email protected]) > > > http://pgp.mit.edu:11371/pks/lookup?op=vindex&[email protected] > > > < > http://pgp.mit.edu:11371/pks/lookup?op=vindex&[email protected] > > > > > > > > > Vote will be open for 72 hours > > > > > > [ ] +1 approve > > > [ ] +0 no opinion > > > [ ] -1 disapprove (and reason why) > > > > > > -Steve > > > > > > -- > > > CONFIDENTIALITY NOTICE > > > NOTICE: This message is intended for the use of the individual or > entity > > to > > > which it is addressed and may contain information that is confidential, > > > privileged and exempt from disclosure under applicable law. If the > reader > > > of this message is not the intended recipient, you are hereby notified > > that > > > any printing, copying, dissemination, distribution, disclosure or > > > forwarding of this communication is strictly prohibited. If you have > > > received this communication in error, please contact the sender > > immediately > > > and delete it from your system. Thank You. > > > > > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >
