I think we should go with the hack. At least for the projects where
I'm involved, being able to generate selective javadocs is a big
selling point for the audience annotations.
-busbey
the contents of this email should be treated as NOT A CONTRIBUTION
under the ALv2.
On Sat, Apr 9, 2022 at 9:46
great narrative context.
On Mon, Dec 7, 2020 at 11:23 AM Allen Wittenauer wrote:
>
>
> ## Description:
> The mission of Yetus is a collection of libraries and tools that enable
> contribution and release processes for software projects
>
> ## Issues:
> There are no issues requiring board
+1
- verified signatures
- verified checksums
- verified src tarball matched expected git ref contents (after
stripping some end-of-line marker stuff that I presume is caused by me
being on windows)
- browsed site tarball (these don't mention that "in progress" is the
0.13 docs on purpose IIRC)
28, 2020, at 9:47 AM, Sean Busbey wrote:
> >
> > shoot man I totally missed this vote call because out of all the yetus
> > related emails *only this one* got flagged by gmail as "not
> > important".
> >
> > I'll get a vote in this evening. Probably wort
shoot man I totally missed this vote call because out of all the yetus
related emails *only this one* got flagged by gmail as "not
important".
I'll get a vote in this evening. Probably worth pinging a few folks
off channel or via private@ in case others also use gmail for reading
the list and
Excellent! Thanks Allen!
On Sun, Oct 18, 2020, 15:25 Allen Wittenauer wrote:
>
> The OS X homebrew tap is unusable at the moment due to the URL we use in
> it being broken.
>
> I'm sure I'm not the only one who has noticed, when it did work, how slow
> it was... so I've filed YETUS-1033 to not
+1
On Sun, Sep 6, 2020 at 1:56 PM Allen Wittenauer
wrote:
>
> Let's finish this up... Using Majority Approval:
>
> [ ] +1 Rename the branch
> [ ] +0 no opinion
> [ ] -1 Do not rename because
>
>
> Vote closes on Friday.
>
> Thanks.
>
looks great.
On Sun, Sep 6, 2020 at 12:04 PM Allen Wittenauer
wrote:
>
>
>
>
> > On Sep 3, 2020, at 7:33 PM, Sean Busbey wrote:
> >
> > Looks good. Thanks for the write up Allen!
> >
> > Maybe a mention about our move off of builds.a.o?
> >
Looks good. Thanks for the write up Allen!
Maybe a mention about our move off of builds.a.o?
On Thu, Sep 3, 2020, 20:49 Allen Wittenauer
wrote:
> Thanks!
>
>
> ===
>
> ## Description:
> The mission of Yetus is the creation and maintenance of software related
> to
> libraries and tools that
I'm skeptical on capacity, but we don't need much for our own tests iirc.
Let's try it out.
On Wed, Aug 19, 2020, 15:06 Nick Dimiduk wrote:
> I'm fine with moving to GitHub actions. The experiment you posted up looked
> pretty nice. I'm not clear on how resources are allocated from GitHub, but
I'd be glad for us to change both our default for development and the
default we use for test-patch.
To minimize the learning curve for new contributors I'd say we should
go with whatever GitHub changes the default to. I haven't seen
anything on the main github site, but the article you linked
looks great to me.
On Sat, Jun 6, 2020 at 4:55 PM Allen Wittenauer wrote:
>
>
> Let me know if I missed anything of importance. Thanks!
>
> ===
>
> ## Description:
> The mission of Yetus is the creation and maintenance of software related
> to
> Collection of libraries and tools that enable
+1 thanks for driving this RC Allen!
On Mon, Apr 13, 2020 at 7:28 PM Allen Wittenauer wrote:
>
>
> Artifacts are available:
>
> https://dist.apache.org/repos/dist/dev/yetus/0.12.0-RC1/
>
> As of this vote the relevant sha512 hashes are:
>
> SHA512 (CHANGELOG.md) =
>
I would love to see 0.12 get out the door. There's nothing else I can
think of that can't wait for another release.
On Sat, Apr 4, 2020, 13:40 Allen Wittenauer
wrote:
>
> Hey gang.
>
> IMO, I'd like to re-start getting a 0.12.0 release out the door.
>
> There are two issues
the HBase side, I think I follow your meaning. Let me see if I can make
> the change you describe.
>
> Thanks,
> Nick
>
> On Sat, Feb 8, 2020 at 8:45 PM Sean Busbey wrote:
>
> > I think that's because hbase has the qabot set to use both jira and GitHub
> > plugin
I think that's because hbase has the qabot set to use both jira and GitHub
plugins.
Since the hbase project has different Jenkins runs for handling jira and
GitHub, we should just configure each to skip the other's plugin.
On Fri, Feb 7, 2020, 12:18 Nick Dimiduk wrote:
> Heya,
>
> What's with
If someone can give me a review on this trivial patch, it's blocking 0.12:
https://github.com/apache/yetus/pull/84
On Wed, Jan 8, 2020 at 12:48 PM Sean Busbey wrote:
> This obviously didn't happen. Sorry folks, inaccurate guess about how I'd
> be spending my holiday time.
>
> I'll
This obviously didn't happen. Sorry folks, inaccurate guess about how I'd
be spending my holiday time.
I'll pick this up again next week.
On Sun, Dec 22, 2019, 14:27 Sean Busbey wrote:
> I'm planning to spin up a new release candidate this week off of the
> master branch. If you have c
I'm planning to spin up a new release candidate this week off of the master
branch. If you have changes pending that you'd like to see land please drop
a note on this thread and I'll prioritize a round of reviews prior to
making the first candidate.
It's on purpose. If you pass the cli option:
--run-tests
Then it'll run unit tests. The option is also activated by --robot and
--sentinel
I'm not sure if it's triggered by the auto CI system detection.
For humans it's covered by the very end of the intro section on "enabling
features"
The Apache Software Foundation and the Apache Yetus Project are pleased to
announce the release of version 0.11.1 of Apache Yetus.
Apache Yetus is a collection of libraries and tools that enable contribution
and release processes for software projects. It provides a robust system
for
The PR for the website update for 0.11.1 is up:
https://github.com/apache/yetus/pull/77
After that I can announce and start the process for 0.12.
(note that a review from any contributor is binding; if you're reading
this you can help. :) )
With three +1s and no other votes, this VOTE passes.
Thanks everyone!
On Tue, Oct 29, 2019, 23:23 Sean Busbey wrote:
> Artifacts are available:
>
> https://dist.apache.org/repos/dist/dev/yetus/0.11.1-RC1/
>
> As of this vote the relevant sha512 hashes are:
&
Thanks for bringing up these issues Clay. The website has been a
source of consternation for awhile. I'll try to answer stuff below,
but in general if you have opinions on moving this stuff around I know
we'd be game.
On Tue, Oct 22, 2019 at 12:31 AM Clay B. wrote:
>
> I have expanded the docs
Artifacts are available:
https://dist.apache.org/repos/dist/dev/yetus/0.11.1-RC1/
As of this vote the relevant sha512 hashes are:
CHANGELOG.md
a3d5a47eee3c23cf3e98e467e7ce6710236daa8653397126e2c02da69ad7cb8b2280ad62dc8960f712b88c59f7a1cb97fa2345ebb9c35d77a86c9d54182b2916
RELEASENOTES.md
I would love to have an API compatibility check in Yetus.
IIRC, the key issue that we got stuck on in YETUS-445 was how we provide such a
tool. All of the foundational libraries for JVM compatibility (jdiff, JACC) are
under a license that the foundation has deemed "category-x". That means that
Looks great Allen! Thanks for putting this together.
You got slides for that Apachecon talk? Was it recorded?
On Tue, Sep 10, 2019, 17:25 Allen Wittenauer wrote:
> Hmm. I guess I should add the talk I’m doing at ApacheCon today. haha.
>
> > On Sep 10, 2019, at 10:02 AM, Allen Wittenauer
The Apache Software Foundation and the Apache Yetus Project are pleased to
announce the release of version 0.11.0 of Apache Yetus.
Apache Yetus is a collection of libraries and tools that enable contribution
and release processes for software projects. It provides a robust system
for
+1
On Fri, Aug 23, 2019, 22:55 Sean Busbey wrote:
> Artifacts are available:
>
> https://dist.apache.org/repos/dist/dev/yetus/0.11.0-RC1/
>
> As of this vote the relevant sha512 hashes are:
&
Artifacts are available:
https://dist.apache.org/repos/dist/dev/yetus/0.11.0-RC1/
As of this vote the relevant sha512 hashes are:
CHANGELOG.md
d864d7ee8ff8bf41db42e052a41e182c95fc8509cc82dbab5d7207c53dc4f0992798849b3e5ae126a54487cf599e6485290a4c12055957a5e1cbb5b74afbb68b
RELEASENOTES.md
t crippled here.
>
> Sent from my ️
>
> > On Aug 21, 2019, at 3:27 PM, Sean Busbey wrote:
> >
> > At the moment I believe a project's personality could call
> > add_header_line and add_footer_table to put stuff before/after the
> > detailed vote, but it's used a
copying everything an then modifying
the _finalreport implementation.
On Wed, Aug 21, 2019 at 2:20 PM Sean Busbey wrote:
>
> I would love a template since it would mean if we wanted we could
> include more than just a link to the contribution guide (and include
> it all the time rather th
I would love a template since it would mean if we wanted we could
include more than just a link to the contribution guide (and include
it all the time rather than just when branch detection fails). oh!!!
does the github PR api include if the PR is a first contribution?
because if it does and
+1
* checked signatures
* checked sums
* checked RELEASENOTE / CHANGELOG
* spot checked the maven repo for expected artifacts
* spot checked LICENSE/NOTICE
- the LICENSE/NOTICE section for Jython is wrong (but since I
can't find us actually including it in any of the posted artifacts I
think
If I can edit in markdown then I'm happy with whatever.
I already maintain a middleman install just for yetus. I don't mind
whatever replaces it if I get to uninstall middleman.
On Mon, Apr 22, 2019, 09:50 Allen Wittenauer wrote:
>
>
> > On Apr 21, 2019, at 6:57 PM, Sean B
I really like editing and authoring in markdown. Is there a maven site
plugin to allow that or are we back to some xml stuff?
On Fri, Apr 19, 2019, 11:17 Allen Wittenauer wrote:
>
> While working on YETUS-856, I determined that our version of
> Middleman doesn’t actually seem to fully
HBase has been slowly adopting 0.9.0 and no blockers so far. hopefully
that'll make it easy for me to test 0.10.0 RCs.
On Wed, Apr 10, 2019 at 2:02 PM Allen Wittenauer
wrote:
>
>
> I’m thinking about starting the release process for 0.10.0 this weekend. Any
> comments, questions, concerns?
>
+1 for anything other than dev or private.
On Sat, Mar 23, 2019, 12:47 Allen Wittenauer wrote:
> INFRA is making me run a vote:
>
> +1 - send all of that stuff to gitbox@yetus
> -1 - no, keep flooding this mailing list
>
> Will close it on Wednesday.
>
> Thanks.
>
thanks for the heads up! I'll try to transition some more stuff moved
over to 0.9.0 in the next couple of weeks in the hope of providing
some useful feedback while it can still be useful in time.
On Thu, Feb 28, 2019 at 12:18 PM Allen Wittenauer wrote:
>
>
> I’m looking to get us back on
heads up, since this could impact Release Doc Maker. I haven't done a
pass of the code yet. Will try to find time this week.
-- Forwarded message -
From: Daniel Gruno
Date: Sun, Jan 27, 2019 at 11:10 AM
Subject: [Notice] Rate limiting in effect on JIRA, BZ, Moin
To:
This is excellent! Thanks for writing it up!
On Thu, Jan 24, 2019, 11:51 Allen Wittenauer
> This is a ‘get your feet wet’ type of post and doesn’t really cover all
> that Yetus can do. But it hopefully provides a basic groundwork,
> especially for those looking for GitHub pull request support.
oh and I almost forgot YETUS-776
On Wed, Jan 16, 2019 at 3:13 PM Sean Busbey wrote:
>
> +1 (binding)
>
> ran into two things that I don't think need to be blockers, filed as
> YETUS-774 and YETUS-775.
>
> On Thu, Jan 10, 2019 at 11:38 AM Sean Busbey wrote:
> >
> &
On Thu, Jan 10, 2019 at 12:26 PM Allen Wittenauer
wrote:
>
>
>
> > On Jan 10, 2019, at 10:12 AM, Sean Busbey wrote:
> >
> > Excellent. Thanks for putting together this RC. So far I've just been
> > reading RN and looking at the shape of the artifacts.
> &
Excellent. Thanks for putting together this RC. So far I've just been
reading RN and looking at the shape of the artifacts.
Given:
> releasedocmaker and shelldocs are now available as Jython-built jars.
why don't these show up in the staged maven repo?
On Thu, Jan 10, 2019 at 11:14 AM Allen
Thanks Allen!
On Sat, Dec 15, 2018, 08:58 Allen Wittenauer
>
> > On Dec 14, 2018, at 8:41 PM, Allen Wittenauer
> >
> wrote:
> >
> > As Sean mentioned in the other thread, he wasn’t sure if he filed it.
> It doesn’t look like he did, so I filed
>
I don't think I've filed the INFRA jira, but it's been a long week.
On Fri, Dec 14, 2018, 11:24 Allen Wittenauer
>
> > On Dec 13, 2018, at 4:52 PM, Allen Wittenauer
> >
> wrote:
> >
> > a) create some Yetus-specific GitHub credentials (that the PMC will have
> access to)
> > b) create a Github
Early January sounds good to me. I'm unlikely to find time before then to
run one myself.
Given the improvements queued here for using yetus outside of the ASF, what
would remain for us to cross into 1.0+ versioning?
On Fri, Dec 14, 2018, 11:39 Allen Wittenauer
Speaking of 0.9.0...
>
> Unless
> Combined with other changes, the Docker images will hopefully reduce
project adoption on services such as Circle CI, Travis CI, and GitLab CI in
addition to more traditional Jenkins shops now utilizing Docker.
I think you mean "reduce barriers to project adoption" or "increase project
any one have concerns they want to weigh in with about moving to gitbox per
INFRA's email to dev@?
if no one has objections, I'll take care of filing the INFRA ticket.
+1
On Thu, Dec 6, 2018 at 1:40 PM Allen Wittenauer
wrote:
>
>
> Based upon the previous discussion, let’s call a vote on changing our commit
> policy:
>
>
> ===
>
> Apache Yetus will allow commits to the source utilizing a Lazy Consensus
>
On Tue, Dec 4, 2018 at 11:14 AM Allen Wittenauer
wrote:
>
>
> > On Dec 3, 2018, at 9:09 PM, Sean Busbey wrote:
> >
> > I found a pro-RTC message I did in another community. Here it is below
> > just barely updated for here:
>
> Good stuff! Comments
nts
above.
---
I still think these three points are true for the majority of the open
source work I've participated in.
That said, if I'm going to give CTR another try anywhere I'd rather it
be here in Apache Yetus. So please consider my -0 changed to +1.
On Mon, Dec 3, 2018 at 10:46 PM Sean Busbey
FYI, I have some Yetus time coming up with the holiday. Anyone have
opinions on how I should prioritize reviews? Ideally I'd like to do
what I can to get us closer to a releasable master branch.
Absent some ideas I'll probably just march through things in Patch
Available oldest to newest.
+1 sounds great to me.
On Sat, Nov 17, 2018 at 4:49 PM Allen Wittenauer
wrote:
>
> In order to make lives easier for our users, Apache Yetus will start
> releasing Docker hub images (apache/yetus and apache/yetus-base) such that
> apache/yetus-base includes the requirements for running Apache
"latest" sounds like something a downstreamer should use to stay up to
date, so I'd rather have it track release and name the current master
branch image "master".
Otherwise sounds good.
On Tue, Nov 13, 2018, 12:41 Allen Wittenauer
>
> > On Nov 13, 2018, a
Awesome! Do we have any kind of timeline to a release that includes this?
I'd like to get one going sooner rather than later so that downstream folks
can update with fewer new things that might be the cause of any
frustrations, since project restructuring is high risk for causing problems.
On
How do we delineate between images meant for downstream (i.e. releases) vs
those only for use when working on yetus (branches)?
On Mon, Nov 12, 2018, 00:53 Allen Wittenauer
>
> YETUS-683 proposes to start publishing convenience binaries as
> images at hub.docker.com. Included with
I'm seeing some behavior and I don't know if my expectations are wrong
or if something is amiss in how Yetus relaunches under docker.
I've got a project specific Dockerfile that's trying to use jdk7 from
Azul Systems.
In my Dockerfile, I install the jdk and attempt to make sure it's seen
as
Before we hit 1.0 I'd want a formalization of what we're saying the
compatibility expectations are for everything we publish.
For example, we've changed the output of release doc maker a couple times.
Would we need to stop doing that?
I've seen Allen mention a Jenkins plugin a couple of times
+1 (binding)
* verified signatures
* verified checksums
* verified source tarball corresponds to given git ref
* spot read of LICENSE files and release notes
* tried building src
* tried using bin on a few hbase jiras locally
* ran through using releasedocmaker
Incidentally the maven staging
Could we extend this by a day or so? I was planning to test last night
/ this morning but life happened.
On Fri, Aug 24, 2018 at 9:11 AM Allen Wittenauer
wrote:
>
> Artifacts are available:
>
> https://dist.apache.org/repos/dist/dev/yetus/0.8.0-RC1/
>
> As of this vote the relevant sha512 hashes
On Tue, Aug 21, 2018 at 10:51 PM Allen Wittenauer
wrote:
>
>
>
> > On Aug 21, 2018, at 7:19 PM, Sean Busbey wrote:
> >
> > Do we know if anyone at the ASF is still relying on 0.4.0 or 0.5.0?
> > It'd be good to proactively check if a specific issue i
yay for 0.8.0! I have "community time" marked on my calendar for
friday morning in central time. I can get a round of reviewing in
then, though it's cutting it close.
Do we know if anyone at the ASF is still relying on 0.4.0 or 0.5.0?
It'd be good to proactively check if a specific issue is
nice!
have the yetus project account retweet?
On Wed, May 23, 2018 at 2:12 PM, Allen Wittenauer
wrote:
> FYI.
>
>
> Based upon a Twitter comment about difficulties in using patch from aphyr, I
> wrote up a quick (with probably a ton of errors as a result…. haha)
Hi folks!
I'd like to get a 0.8.0 release out soon so that YETUS-622
"docker-cleanup removes non-Yetus docker images even if not in
sentinel mode" is available in a release.
I'm happy to RM that release. Prior to doing so, I'm hoping to get in
a few changes that impact plans in the Apache HBase
looks like another build earlier that day on the same host hung for 12 hours:
https://builds.apache.org/job/PreCommit-Admin/13059/
Both jobs look to be failing during the jenkins git plugin due to
resource exhaustion. IIRC, that plugin is before the timeout starts
counting.
I suspect if we
Anyone have concerns with me replacing our existing .md5 files with
the sha512s previously published in our aggregate .mds files?
Anyone prefer if I just add them and don't remove the .md5 files?
+1 binding
* check signatures / hashes of dist and maven staging
* spot check on LICENSE / NOTICE
* top level build on source artifact works on my system (though my
python / ruby / maven stuff just got tweaked while working on some
yetus stuff)
* works-at-all check on wrapper scripts (with notes
?
> python -c "import ssl; print ssl.OPENSSL_VERSION"
>
> The issue is with the OpenSSL being packaged with OSX. The version of
> OpenSSL needs to be higher than 1.0.0
>
> Some of the workarounds I have seen work are upgrade OpenSSL , use a
> virtual environment, upgrade
Just want to make sure I'm not missing something obvious before filing
a JIRA. current master's releasedocmaker should work with on our
tracker right?
Busbey-MBA:target busbey$ ../release-doc-maker/releasedocmaker.py
--project=YETUS --version=0.4.0 --projecttitle="Apache Yetus"
--dirversions
FYI Duo, I believe
https://issues.apache.org/jira/browse/YETUS-594
is also slated to fix this. it just needs a review.
On Tue, Jan 16, 2018 at 4:38 AM, Duo Zhang wrote:
> Started from this build
>
> https://builds.apache.org/job/PreCommit-Admin/329113/
>
> Have dug a bit,
I can dedicate some review time this evening ~11pm Central. If anyone
has review time prior to that feel free to jump ahead. :)
On Tue, Jan 16, 2018 at 10:43 AM, Allen Wittenauer
wrote:
>
> I just uploaded a new version of YETUS-594 which fixes a bug the
>
The Apache Software Foundation and the Apache Yetus Project are pleased to
announce the release of version 0.6.0 of Apache Yetus.
Apache Yetus is a collection of libraries and tools that enable contribution
and release processes for software projects. It provides a robust system
for automatically
With four +1s (three binding) and no other responses, this vote passes.
Thanks folks!
On 2017-10-27 01:20, Sean Busbey <bus...@apache.org> wrote:
> Hi folks!
>
> Artifacts are available:
>
> https://dist.apache.org/repos/dist/dev/yetus/0.6.0-RC1/
>
> As of this v
f. The build
> runs perfectly fine.
>
> My vote is non-binding.
>
> Thanks
>
> -Suraj Acharya
>
> On Thu, Oct 26, 2017 at 11:20 PM, Sean Busbey <bus...@apache.org> wrote:
>
>> Hi folks!
>>
>> Artifacts are available:
Hi folks!
Artifacts are available:
https://dist.apache.org/repos/dist/dev/yetus/0.6.0-RC1/
As of this vote the relevant md5 hashes are:
fac98675fd631d4ddedce50935938000 CHANGES.md
96b3fd3de50cb41717d5f20a7a432de8 RELEASENOTES.md
93ed47909c5f0ea71b40ff52a45dd221 yetus-0.6.0-bin.tar.gz
Yeah, YETUS-553 is probably ready to go. I was trying it on hbase
stuff, but enough stuff fell over around the change of oracle jdk8
versions that I've barely touched it.
On Mon, Oct 23, 2017 at 9:31 AM, Allen Wittenauer
<a...@effectivemachines.com> wrote:
>
>> On Oct 22, 2017, at
I'd like to start rolling a release soon. I'm happy to build a 0.5.1
at the same time as a 0.6.0.
Is there anything folks would like included in 0.5.1 other than YETUS-544?
On Fri, Oct 13, 2017 at 1:47 PM, Sean Busbey <bus...@apache.org> wrote:
> YETUS-534 added personality_parse_ar
YETUS-534 added personality_parse_args, which feels like enough to
justify a new minor release.
If we're going to cut a release off of current master, we should get
YETUS-556 in.
On Fri, Oct 13, 2017 at 10:57 AM, Allen Wittenauer
wrote:
>
> We need to get
Hi folks!
At last week's board meeting, the board approved a proposal to shift
the chair of the Yetus PMC from me to Allen. Let's take a moment to
congratulate him on this new role.
Thanks for stepping up Allen! If there's anything I can help with, let me know.
awesome. thanks for taking care of this Allen!
On Sun, Sep 10, 2017 at 11:03 PM, suraj acharya wrote:
> +1
>
> On 10 Sep 2017 8:55 pm, "stack" wrote:
>
>> +1
>>
>> Two paragraphs above releases section need a re-read; they are missing
>> articles.
>>
>>
sounds like the seed for a good blog post. :)
On Fri, Aug 18, 2017 at 1:00 PM, Andrew Wang wrote:
> Kudos Allen!
>
> On Aug 18, 2017 10:36 AM, "Allen Wittenauer"
> wrote:
>
>>
>> It’s always amazing watching sentinel mode kick in on the
-dev@yetus to bcc, since I think this is a Hadoop issue and not a yetus
issue.
Please review/commit HADOOP-14686 (which I am providing as a
volunteer/contributor on the Hadoop project).
On Tue, Jul 25, 2017 at 7:54 PM, Allen Wittenauer
wrote:
>
> Again: just
Okay, so two different feature requests. :)
On Fri, Jul 14, 2017 at 2:51 PM, Allen Wittenauer
<a...@effectivemachines.com> wrote:
>
>
> > On Jul 14, 2017, at 8:01 AM, Sean Busbey <bus...@apache.org> wrote:
> >
> > I think that the lack of a vote from jd
I want to make sure I'm thinking about things correctly before filing
issues.
In HBase I'm setting up nightly jobs that rely on Yetus in QBR mode. On
some of our branches, we support both jdk7 and jdk8 so I want to run unit
tests for both. I'm currently using 0.5.0.
Here's the report from two
Okay, I'll rephrase that bit and post.
On Jul 13, 2017 12:43 PM, "Allen Wittenauer" <a...@effectivemachines.com>
wrote:
0.5.0 will get announced later this afternoon, so might as put that in the
report.
Other than that, +1. :)
> On Jul 12, 2017, at 11:07 AM, Sean Busbey
Here's a draft of our report for this quarter (off cycle due to missing
last month, fyi)
Apache Yetus provides libraries and tools that enable contribution and
release processes for software projects.
ISSUES FOR THE BOARD'S ATTENTION
We missed our report last month due to the PMC Chair
+1
* checked signatures
* checked checksums
* source corresponds to given repo commit
* ran build on source
* works-at-all tests on bin
* skimmed licensing
* read release notes and changes
On Fri, Jul 7, 2017 at 11:09 PM, Allen Wittenauer wrote:
> Hello Everyone! It's VOTE
FWIW, my plan was to vote this morning but life circumstances are making
that difficult.
Let's plan to extend to the end of the week?
On Jul 10, 2017 22:34, "Allen Wittenauer" wrote:
>
> Just a reminder:
>
> there is less than 24 hours left on this vote and there
Hi Peter!
If Hive is still figuring out what it would prefer in its personality, then
probably best to finish it up and get it into the next release.
I'd like us to into a better habit of releasing as a community, so anything
that's made it into the code base in a few weeks time will be enough
<a...@effectivemachines.com>
wrote:
>
> > On Jul 6, 2017, at 4:35 PM, Allen Wittenauer <a...@effectivemachines.com>
> wrote:
> >
> >
> >> On Jul 6, 2017, at 3:42 PM, Sean Busbey <bus...@apache.org> wrote:
> >>
> >> The patches are all generate
I have a patch that keeps failing to apply in yetus test-patch:
https://issues.apache.org/jira/browse/HBASE-18327
I've tried regenerating the patch with git diff instead of format-patch,
I've tried using both the 0.4.0 release of yetus as well as the current
master branch. no joy.
The patches
that's an excellent reason for me to prioritize getting that yetus release
out first. thanks!
On Thu, Jul 6, 2017 at 11:47 AM, Allen Wittenauer <a...@effectivemachines.com>
wrote:
>
> > On Jul 5, 2017, at 9:26 PM, Sean Busbey <bus...@apache.org> wrote:
> >
> > I
I'm trying to set up a new Jenkins declarative pipeline that uses
test-patch's nightly mode. I'm trying to rely on docker for all the tooling
I can.
My first attempt has failed because the worker environment has no maven. I
can add it in, but I expected that to come from my dockerfile (that has a
having the ability to switch between JACC and japicmp would be great. It
would nicely deal with teh largest concern from YETUS-445, the hard
dependency on something with a category-x license.
On Wed, Jul 5, 2017 at 12:58 PM, Ray Chiang wrote:
> Greetings fellow devs,
>
>
let's use the easy path for the default yetus dockerfile. Sounds like
that's Ubuntu 16 and openjdk8.
On Sun, Jun 4, 2017 at 12:27 PM, Allen Wittenauer
wrote:
>
> Folks, we need to make a decision here. Currently, precommit for yetus itself
> is completely broken
o if we want to stick with 7, then that means sticking with Trusty.
>
>> On May 31, 2017, at 1:06 PM, Sean Busbey <bus...@apache.org> wrote:
>>
>> I'd love a 0.5.0 release, FWIW.
>>
>> Would pulling down openjdk 7 artifacts go more reliably? That would
>>
I forwarded Allen's note over to HBase as well. no responses yet.
On Tue, May 30, 2017 at 10:26 AM, Allen Wittenauer
wrote:
>
>
> Just to bring this back around:
>
> I've got a patch sitting on YETUS-509 to remove the support for
> testing Maven's eclipse
I'd love a 0.5.0 release, FWIW.
Would pulling down openjdk 7 artifacts go more reliably? That would
presumably be a bit less disruptive than also jumping to jdk8.
(for clarity, I don't think this is too aggressive, since the default
is just an exemplar and folks could always roll their own.)
On
t;
> Can I just modify dev-support/docker/Dockerfile in my patch and that would
> be picked up?
>
>
> Sean Busbey wrote:
>>
>> +dev@yetus in case some other community has run into this.
>>
>> Yetus is supposed to age out images after a time. Do we know abo
1 - 100 of 157 matches
Mail list logo