Am 03.07.20 um 22:16 schrieb Werner Keil:
> Isn't Tamaya going to be ramped down?
Sorry for the noise, I just pushed an old branch in order to be able to
switch branches.
But I'm going to disable the regular builds for extensions as we ran
into a problem after JDK8 was updated from _142 to _152 .
ep using the name "Tamaya" we probably have to
> abandon it and find a new one.
>
>
> Werner
>
>
>
>
> On Thu, Apr 30, 2020 at 11:20 PM Werner Keil wrote:
>
>> Hi,
>>
>> I also moved but it's already done, so I should be able to
Hi all,
as I'm in the middle of moving I won't be able to do that much until end
of June, but my github id is "ottlinger".
Thanks and stay happy&safe everybody!
Cheers,
Phil
it to the
> IPMC to vote?
>
> Thanks,
>
> John
>
>
> On Thu, Apr 16, 2020 at 5:28 AM P. Ottlinger <mailto:pottlin...@apache.org>> wrote:
>
> Hi *,
>
> following our discussions in January and February 2020 I propose to
> term
Am 16.04.20 um 11:28 schrieb P. Ottlinger:
> Hi *,
>
> following our discussions in January and February 2020 I propose to
> terminate/retire Apache Tamaya podling and move all repositories over to
> Github and remove all references to Apache Software Foundation after that.
&g
Hi *,
following our discussions in January and February 2020 I propose to
terminate/retire Apache Tamaya podling and move all repositories over to
Github and remove all references to Apache Software Foundation after that.
Vote is open until 2020-04-20.
[ ] +1 Please proceed with the steps above
Hi everybody,
I do hope that all of you are fine amid the current situation .
do we want to proceed with the termination of Tamaya?
@Justin:
as there is not attic for Incubator projects - can we just move the
source code to a public github repo and continue there?
OR do we need the board to a
Hi,
Am 10.02.20 um 22:29 schrieb Oliver B. Fischer:
> But looking at the number of commits, Tamaya is dying.
LOL - Anatole is and was the main contributor and committer -
this did not change over the period Tamaya is in incubating mode, IMHO.
> What do you thing, does Tamaya currently provides a
Hi *,
Am 10.02.20 um 16:11 schrieb Oliver B. Fischer:
> who would describe themselves as an active committer?
Although I do not contribute that much code I'd consider myself an
active committer.
@John: the release is officially out, we just did not announce it
properly due to the fact that we se
Hi guys,
following our discussions I submitted our February report
https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#tamaya
Cheers,
Phil
Am 16.01.20 um 01:27 schrieb jmcl...@apache.org:
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> In
Hi everyone,
should we add our discussion to the February report? Or just add a
sidenote (apart from releasing 0.4) that there are discussion about the
project's future?
Thanks,
Phil
Hi,
Am 17.01.20 um 20:57 schrieb Anatole Tresch:
> Honestly, I am opem to anything. Time actually is rare and I will not have
> much in the next months either. We can think to move everything to GH and
> continue there as time allows...
The disadvantage of that would be we loose the umbrella of A
Hi guys,
anything noteworthy to report?
The discussion I tried to start about the future of Tamaya did not yield
any results yet .
@dev: any feelings about the future of Tamaya?
We seem to lack new PMC members, committers and contributors for quite a
while.
Cheers,
Phil
Am 16.01.20 um 01:2
Merged :-)
Thanks and happy new year to everyone
Phil
Am 31.12.19 um 16:18 schrieb P. Ottlinger:
>> https://github.com/apache/incubator-tamaya-sandbox/pull/32
Hi Aaron,
did we release sandbox modules as well?
If so, we could update to the newer SNAPSHOT.
Thanks,
Phil
Am 31.12.19 um 16:16 schrieb Aaron Coburn:
> I believe the extension modules are all set -- they were part of the 0.4
> release and they have been incremented to 0.5-incubating-SNAPSHOT.
Hi everyone,
the sandbox modules do not seem to build anymore as the 0.4-SNAPSHOT
seems unavailable as 0.4 is released - should sandbox and extensions
migrate to 0.4 instead?
Cheers,
happy new year
/Phil/
Hi,
in order for a Jira release of 0.4 we should scan the following 33 tickets:
JQL:
project = Tamaya and (fixVersion = "0.4-incubating" or fixVersion is
EMPTY )and status in (Open, "In Implementation", "In Progress", "In
Review")
https://issues.apache.org/jira/issues/?jql=project%20%3D%20Tamay
Hi,
I finished the homepage rework.
Please have a look for errors ;)
I regenerated the homepage with APIdocs and removed the old voting
branches in tamaya-site repo.
Have fun,
Phil
Hu guys,
great work :)
Am 11.11.19 um 20:18 schrieb Anatole Tresch:
> The only thing *left over is updating the
> homepage* and *preparing the master for the next snapshot*
> 0.5-incubating-SNAPSHOT
I'll take care of the homepage in the coming days ... stay tuned for Git
mails ;)
Thanks,
Philip
Am 06.11.19 um 08:39 schrieb Julian Feinauer:
> Hi, we just got the final 2 IPMC Votes, so you can finally finish of the
> Release Anatole!
@Julian,
thanks :-)
I did not change the board report but this gives us the chance to
report something in the next cycle.
@Anatole: I'm on a trade fai
Am 02.11.19 um 21:43 schrieb Anatole Tresch:
> The vote is still open on the general list, so we cannot proceed with the
> release as of now. We need two additional +1 votes.
> We can mention that in the report ;-)
Submitted the report:
https://cwiki.apache.org/confluence/display/INCUBATOR/Novembe
Ping?
Any news concerning our release candidate?
Otherwise I will just file a report.
Cheers,
Phil
Am 25.10.19 um 21:10 schrieb P. Ottlinger:
> I'll take care of the report -
> hopefully we can add our release to the list of achieved stuff.
>
> @Anatole: did the vote already
I'll take care of the report -
hopefully we can add our release to the list of achieved stuff.
@Anatole: did the vote already pass?
Cheers & happy weekend
Phil
Am 20.10.19 um 14:27 schrieb jmcl...@apache.org:
> The board meeting is scheduled for Wed, 20 November 2019, 10:30 am PDT.
> The report
Hi,
the podling report reminder reminded me of our RC ... what needs to be
done to get the release officially out?
If the formal vote is over I'd love to do the homepage changes.
What else needs to be done?
Thanks,
Phil
Hi guys,
just reading Sally's weekly newsletter:
ApacheCon™ – the ASF's official global conference series, bringing
Tomorrow's Technology Today since 1998
- *T-18 days* to ApacheCon Europe
--TRACKS in Big Data, Cloud, Community, IoT, Machine Learning, Open
Source Design, Servers, and more.
Hi,
Am 02.10.19 um 01:55 schrieb jmcl...@apache.org:
> This should be appended to the Incubator Wiki page at:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/October2019
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
Am 25.09.19 um 14:41 schrieb Anatole Tresch:
> The tag for this release candidate is available at [3] and [4]. It will be
> renamed
> once the vote passed.
> Please take a look at the artifacts and vote!
+1
Works fine in my pet project.
Cheers,
Phil
Hi everybody,
if there are no objections I will file our report tomorrow evening with
the following items:
* new mentor Julian
* 4 release votes, hopefully RC5 will make our new release
Anything else to add?
Thanks,
Phil
Am 23.09.19 um 19:58 schrieb Anatole Tresch:
> Then lets go for rc5. It s not much work...👍
If we go down this path let's *not* create a new branch in the
tamaya-site repo (to not get rid of all the changes already applied to
the latest branch).
WDYT?
Cheers,
Phil
Am 23.09.19 um 12:46 schrieb Julian Feinauer:
> Is anybody wlling to do this?
I volunteer to compile the report :-)
Sorry, have been offline due to hardware trouble and now my working
environment is restored.
Any particular issues to be reported except
* new mentor Julian Feinauer, thanks :-)
*
Am 05.09.19 um 21:00 schrieb Julian Feinauer:
> yeah I think we should have another RC... : /
Should we exclude bnd files and markdown from RAT scans?
I think it does not make sense to pollute the bnd files with license
heeaders.
Cheers,
Phil
Hi,
when I created TAMAYA-411 I asked myself which javadoc versions we
should be keeping?
Does it make sense to only provide:
* the current SNAPSHOT / development version
* the last release(d) version
or should we keep Javadocs from all available versions?
My personal opinion is to keep only 2 v
Am 28.08.19 um 03:00 schrieb Anatole Tresch:
> [ ] +1 for community members who have reviewed the bits
+1
I played with the core artifacts and checked the homepage changes.
Did not look into much detail into sandbox and extensions, but core
looks fine.
Cheers,
Phil
@Anatole:
can you file a report please?
As we are working towards a release there's something to report ;)
Thanks
Phil
Am 31.08.19 um 03:40 schrieb jmcl...@apache.org:
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial remin
Am 29.08.19 um 00:32 schrieb Anatole Tresch:
> Did I have overwritten something? Afaik I just pulled everything and only
> changed the release guide to ensure it works...
All of the changes in the proposed release branch had to be merged into
the new branch (i.e. current release branch in tamaya-
Hi Anatole or other fellow devs,
pls do not override changes made to the release branch of our webpage.
The branch contains some fixes that should not be lost.
https://issues.apache.org/jira/browse/TAMAYA-411 needs to be done once
the vote passes.
Thanks,
Phil
Am 27.08.19 um 20:46 schrieb Aaron Coburn:
> (That key is, in fact, older than the one listed in the KEYS file)
>
> Maybe Julian can advise on whether these are blockers for a release.
As the KEYS are supposed to be the way to authenticate artifacts they
should be correct .. @Anatole: can you
Thanks for your efforts, Anatole!
Am 26.08.19 um 19:22 schrieb Anatole Tresch:
> its rather simple. We have to fix it, and rebuild everything. Takes round
> about ab hour, so I try to do so later.
+1
We must not depend on SNAPSHOTs.
Apart from that the vote thread should have a definite end ...
Am 26.08.19 um 09:54 schrieb Julian Feinauer:
> So, here I am to start a discussion about whether the Tamaya PPMC would like
> to have me on board as mentor : )
>
> Please feel free to express your opinions or ask further questions.
+1
Thanks for your interest in Tamaya -
we are a small podlin
Hi,
Am 19.08.19 um 12:44 schrieb Anatole Tresch:
> If there are no objections, I'll start with the first steps for
> the next release of Apache Tamaya Version 0.4-incubating.
> It will start with the release procedure within this week.
+1
Go ahead :-)
I'm unavailable at the moment sorry an
Am 17.07.19 um 00:16 schrieb Werner Keil:
> The JSR will never be out, it was withdrawn in favor of either MicroProfile
> Config, a future Jakarta spec or both.
> the Jakarta spec is not there but keeping the old JSR in there would cause
> more confusion, in a sandbox module I guess it is at people
Am 16.07.19 um 16:42 schrieb Anatole Tresch:
> the jsr382 module is in the sandbox and can be deleted or just removed from
> the build. Any new abstractions from the jsr have been moved to the
> microprofile api, but were not yet released, so the code written there will
> be of great use once the n
Am 27.05.19 um 21:46 schrieb Werner Keil:
> Because we (Anatole as well) already have DWX in June, I can't say for next
> month, unless we did get a mandatory workshop in Berlin with the partner
> company.
I could offer being a "JUG"-host in the middle of Berlin with max 20-35
people attending.
Hi,
I could provide a location for a not too big meetup
just let me know, Oliver+Werner :-)
Cheers,
Phil
Am 27.05.19 um 19:49 schrieb Werner Keil:
> If you can at a shorter notice, it would be great. I am not sure when we
> have to be in Berlin, it might be between July and August once, but
Hi,
I'm unavailable on weekends.
Thus my monday proposals
Cheers,
Phil
Am 25.05.19 um 12:12 schrieb Oliver B. Fischer:
> Ping
>
> Am 17.05.19 um 14:42 schrieb Oliver B. Fischer:
>> Would be the 1st of June fine for us?
>>
>> Am 15.05.19 um 11:20 schrieb Oliver B. Fischer:
>>>
Hi guys,
thanks for the reminder to hook the site repo into Travis -
now it's generating the site upon each commit, which allows to easily
fix errors in ASciidoc/other templates.
Have fun :-)
Phil
Hi,
can you have a look at your request and merge in the current master?
https://github.com/apache/incubator-tamaya-site/pull/4
Thanks for your help,
Phil
Hi,
I seem to have restored most of the changes concerning the Sonar
integration - feel free to fix any more warnings/issues :-)
Thanks
Phil
Anatole, I tried to reapply most of the stuff I saw,
please go ahead and fix the new sonar warnings .
https://sonarcloud.io/project/issues?id=apache_incubator-tamaya&resolved=false
I assume your changes in sandbox and extensions did also overwrite some
stuff - can you have a look please?
Tha
Hi Anatole,
a lot of work is missing . pls create a branch and work on that.
Forking is not that easy I guess.
Cheers,
Phil
Am 15.05.19 um 08:03 schrieb Anatole Tresch:
> I did a merge but I also did a reset on the travis before pulling so I do
> not overwrite any changes. I never did a for
Hi all,
can anyone help me with testing that class? I don't really get how to
use the class as the way described in Javadoc does not work.
@Anatole: might this exception be related to your latest changes?
Thanks
Phil
Am 12.05.19 um 00:34 schrieb P. Ottlinger:
> Hi *,
>
> w
Am 14.05.19 um 17:52 schrieb Aaron Coburn:
> Hi All,
> it seems that the sonar integration for the core tamaya repository has been
> removed. Were those commits reverted? Or maybe a force-push? A number of
> the recent changes seem no longer to be present.
@Anatole: where did you checkout? Gitbox
Am 13.05.19 um 21:51 schrieb Oliver B. Fischer:
> Monday and Tuesday I will be in St. Petersburg on vacation. ;-)
what about:
2019-05-27 8pm Berlin time?
Cheers,
Phil
Hi Oliver,
Am 13.05.19 um 21:34 schrieb Oliver B. Fischer:
> a hangout would be a good possibility to get an update on Tamaya. I will
> have a look at my calendar and propose an appointment.
what about next Monday (2019-05-20 8pm Berlin time) -
maybe some of the newer contributors could join as w
Hi guys,
Am 13.05.19 um 13:15 schrieb Werner Keil:
> Any chance for a Tamaya proposal to Apachecon Berlin anyone or is it too
> short notice?
Oliver, great to hear that - welcome back :-)
I'm unavailable for a session at Apachecon, sorry.
Cheers,
Phil
Am 12.05.19 um 18:37 schrieb Anatole Tresch:
> Stay tuned.
cool news -
can you create Jira-tickets for your enhancements :-)
Thanks,
Phil
Hi *,
while reviewing Sonar warnings I stumbled upon
org.apache.tamaya.sysprops.ConfiguredSystemProperties
and thought to add a simple test.
But it seems that I don'T understand how to use that class.
Initializing it as propsed by its Javadoc in a test yields a
*** java.lang.instrument ASSERTIO
Thanks for your input -
I'll migrate all repos to launch Sonar in after_sucess, which means no
broken builds for merge requests.
Cheers & happy coding,
Phil
Am 01.05.19 um 22:57 schrieb P. Ottlinger:
> Hi,
>
> as of TAMAYA-277 I froze the current state as "gold standa
Hi,
as of TAMAYA-277 I froze the current state as "gold standard" for future
builds.
This yields problems due to refactorings that break the coding rules of
SonarCloud, example:
https://github.com/apache/incubator-tamaya/pull/49/checks?check_run_id=116131187
Should we make the sonar quality chec
Am 29.04.19 um 21:28 schrieb P. Ottlinger:
> if you have any objections/additions/comments/errors let me know -
> *until 2019-05-01 12:00 CET* - otherwise I'll put the following report
> on the Wiki:
> https://cwiki.apache.org/confluence/display/INCUBATOR/May2019
Hi folks,
now that the Github integration works so smoothly a also triggered an
integration with dependabot, that allows to automatically have pull
requests for all available dependency and maven plugins.
This should make staying up2date much easier :-)
Working on it ...
https://issues.apache.or
the same token (generated directly after logging in to
SonarCloud) for all 3 jobs, the rest is documented in the ticket:
https://issues.apache.org/jira/browse/TAMAYA-277
Cheers + HTH
Philipp
Am 21.04.19 um 23:13 schrieb P. Ottlinger:
> Hi guys,
>
> I'm working on a Sonarcloud-integra
k like the anchor is missing or
> incorrect.
>
> Good to see a discussion about graduation.
>
> Regards,
> Dave
>
> On 2019/02/02 21:11:54, "P. Ottlinger" wrote:
>> Hi guys,
>>
>> I submitted the following report:
>>
>>
>>
Hi,
if you have any objections/additions/comments/errors let me know -
*until 2019-05-01 12:00 CET* - otherwise I'll put the following report
on the Wiki:
https://cwiki.apache.org/confluence/display/INCUBATOR/May2019
Tamaya
Tamaya is a highly flexible configuration solution based on an modular,
Hi,
personally I like to separate things and wouldn't want to launch
mvn sonar:sonar manually,
therefore I preferred the script integration as said in the Travis docs.
I'm not quite sure if Fabrice has the same understanding of the issues I
encountered while trying to work on a sonar integration
Am 22.04.19 um 21:38 schrieb P. Ottlinger:
> @Aaron, thanks for your hints and ideas
It seems that comments from all three of us seemed to help.
I managed to get green builds that said to have sent data to SonarCloud.
The next code change should prove me right or wrong :-)
During
@Aaron, thanks for your hints and ideas
I tried to apply most of them (as I'm unable to install the travis GEM
locally on my Ubuntu box) I tried the integration via environment variable.
Unfortunately not that successful :(
I also started a thread on bui...@apache.org -
let's see if someone
Hi guys,
is there anything new to report, except:
* infrastructure updates (Checkstyle and Sonar integration)
* new mentor did not yet reply to initial mails or did I overlook any
reply to our introductory mails?
Thanks,
Phil
Am 19.04.19 um 03:23 schrieb jmcl...@apache.org:
> Dear podling,
>
>
Hi,
in case you wondered there's a post commit message linking to Github
alerts that is not working.
I filed a ticket for INFRA:
https://issues.apache.org/jira/browse/INFRA-18257
Cheers,
Phil
Hi,
just tuning in into an Oracle podcast about project Helidon - yet
another/a different approach to configuration in Java Microservices/JEE:
https://helidon.io/docs/latest/#/config/01_introduction
Just to get some inspiration ;)
Helidon doesn't have a Tamaya integration yet, but seems to rely
Hi guys,
I'm working on a Sonarcloud-integration of Tamaya
via TAMAYA-277.
Any new code smells result in red builds.
At the moment only manual uploads are possible as I'm waiting for a hint
from INFRA on how to configure credentials properly (don't want to put
them in .travis.yml and am unsure i
that should be able to generate
> reports identifying all the unused variables.
>
> Aaron
>
> On Mon, Mar 25, 2019 at 4:39 PM P. Ottlinger <mailto:pottlin...@apache.org>> wrote:
Hi,
scanning older Jira tickets I stumbled upon Sonar Integration and filed:
https://issues.apache.org/jira/browse/INFRA-18099
to enable it for all Tamaya repos.
Cheers,
Phil
Hi,
Am 22.03.19 um 05:08 schrieb Aaron Coburn:
> Which modules don't have checkstyle enabled?
Not sure if it's configured but
tamaya-core
has some unused variables, that I'd expect to be marked by Checkstyle.
Is that the case?
e.g.
/tamaya-core/src/main/java/org/apache/tamaya/core/internal/conv
Hi,
just to keep the 4-eye-principle up ...
can someone be so kind to do the merges concerning the RAT updates?
On the way I realized that Checkstyle does not seem to be active in all
modules / tests - wouldn't we want that ;)?
I was playing around with new Eclipse and it showed a lot of warnings
l
Am 05.03.19 um 23:46 schrieb P. Ottlinger:
> Dear Justin,
>
> thanks for the reminder -
>
> I added our report from February with a notice about the missing mentors to
> https://wiki.apache.org/incubator/March2019
>
> @John, David: pls sign-off the report.
>
> T
Dear Justin,
thanks for the reminder -
I added our report from February with a notice about the missing mentors to
https://wiki.apache.org/incubator/March2019
@John, David: pls sign-off the report.
Thanks
Phil
Am 05.03.19 um 22:26 schrieb Justin Mclean:
> Hi,
>
> The report which can be fill
Hi,
Am 23.02.19 um 01:26 schrieb Apache Jenkins Server:
> [INFO] --- maven-checkstyle-plugin:3.0.0:check (checkstyle) @
> tamaya-injection-api ---
> [INFO] There are 4 errors reported by Checkstyle 7.8 with
> buildtools/src/main/resources/checkstyle/style.xml ruleset.
> [ERROR]
> src/main/java/
Am 20.02.19 um 22:18 schrieb Justin Mclean:
> Hi,
>
> As your mentors didn't sign off the report you be asked to report again.
>
> Thanks,
> Justin
>
@mentors:
are you still on the list?
are you still mentors?
We need your help :-)
Cheers,
Phil
Hi Christian,
can you recheck
* https://github.com/apache/incubator-tamaya/pull/41 -
https://issues.apache.org/jira/browse/TAMAYA-381
* https://github.com/apache/incubator-tamaya/pull/42 -
https://issues.apache.org/jira/browse/TAMAYA-383
as all of the PRs were merged now.
Thanks for your feedba
Von: Albretch Mueller
Antwort an: Commons Users List
An: Commons Users List
On 2/10/19, P. Ottlinger wrote:
> Another way to help out (from the ASF universe) would be:
> https://tamaya.apache.org/
I did take a look at tamaya:
https://tamaya.apache.org/features.html
~
To me having
Hi Davem
thanks for your feedback, that I put into:
https://issues.apache.org/jira/browse/TAMAYA-382
Cheers,
Phil
cracks? In the latter case, please list any open issues
that need to be addressed.
* As the project needs a wider audience, maybe mentors with interest
in Tamaya would be welcome.
Cheers,
Phil
Am 27.01.19 um 22:12 schrieb P. Ottlinger:
> Hi everybody,
>
> I'd love to do the
Hi Anatole,
can you add Aaron to the list of TAMAYA-people in Jira.
I don't have any kharma in TAMAYA jira :-)
@Aaron: thanks, I've closed the ticket.
Thanks,
Phil
Am 30.01.19 um 19:59 schrieb Aaron Coburn (JIRA):
>
> [
> https://issues.apache.org/jira/browse/TAMAYA-217?page=com.atlassia
Hi Christian,
thanks for reaching out - I assume that the classes/wrong imports are
due to recent reworks within the API.
Please file a Jira issue so that we can properl attribute any commits to
the issue.
Thanks,
Phil
Am 28.01.19 um 09:56 schrieb Niehues, Christian:
> Hi,
>
>
> I am wonderin
Am 27.01.19 um 01:20 schrieb Aaron Coburn:
> Would you like to see the checkstyle configuration be changed to be more
> strict? (i.e. UPPER_CASE?) That change would bring our configuration
> more in line with the default checkstyle format.
+1 for a more standardized config.
Cheers,
Phil
Hi everybody,
I'd love to do the report :-)
* 2 new contributors added, which rocks.
* homepage overhaul
* working on improving the code and getting some issues done
I wouldn't want to report (again) that we try to release and graduate,
as we should deal with that after 0.4 is out.
Any more thi
Am 18.01.19 um 17:08 schrieb Aaron Coburn:
> In the pull requests for the -extensions and -sandbox repositories, I put the
> checkstyle configuration into a ./buildtools directory that isn't a maven
> project at all, so there is no way it can be deployed or installed as an
> artifact. This struc
Am 17.01.19 um 17:02 schrieb Aaron Coburn:
> What would you all think about adjusting the maven configuration to have
> checkstyle run on each build? Initially, it might make sense to just report
> the errors rather than failing an entire build because of them. I can supply
> a PR for this.
coo
Am 17.01.19 um 21:09 schrieb Aaron Coburn:
> I've noticed that for any Github activity on tamaya-extensions and
> tamaya-sandbox (pull requests, comments, etc), messages are sent to the dev@
> list, but that doesn't seem to apply to activity on the main tamaya
> repository. Is there a missing pa
Dear Aaron,
Am 16.01.19 um 15:40 schrieb Aaron Coburn:
> https://github.com/apache/incubator-tamaya/pull/32
> https://github.com/apache/incubator-tamaya-extensions/pull/25
> https://github.com/apache/incubator-tamaya-sandbox/pull/17
Thanks for all your work - I remember (because I started to do s
Am 16.01.19 um 15:40 schrieb Aaron Coburn:
> And in terms of process, should I be waiting for someone to merge these PRs?
> Or should I push these commits directly to master?
I'll have a look at the PRs - I like reviewing ;-)
Thanks for your contribution -
I'm just not sure whether we can drop h
Am 13.01.19 um 22:35 schrieb ajs6f:
> Tamaya is still in incubation, and hasn't released 1.0. I think this is a
> good time to think long-term and make the API what it should be, even if us
> users have to tap-dance a bit to keep up. We'll all be better for it down the
> road.
+1 for the change
Am 05.01.19 um 21:35 schrieb P. Ottlinger:
> I filed
> https://issues.apache.org/jira/browse/INFRA-17558
Fixed -
resync is visible to the world now :-)
Changes include
* overhauled design and start page, thanks Anatole!
* jbake 2.6.3-update
* Javadoc updates for current 0.4-SNAPSHOT
Pls
Hi!
Lucky me the publication of changes seems to be broken after moving
to Gitbox.
I filed
https://issues.apache.org/jira/browse/INFRA-17558
Lucky us we are not under pressure to get the new page out by the end of
the night :-)
Cheers,
Phil
Hi guys,
as I upgraded jbake I'm keen to publish the latest changes /including
the new start page & teasers/
any objections?
To my mind we should publish the page independent of the project/release
status.
Cheers,
Phil
Am 02.01.19 um 21:05 schrieb P. Ottlinger:
> Thanks for stepping in - I think it would be nice to just scan the open
> jira tickets as not all are in the right place.
https://issues.apache.org/jira/issues/?filter=-5&jql=project%20%3D%20TAMAYA%20and%20resolution%20%3D%20Unresolved%20
Am 02.01.19 um 19:26 schrieb Anatole Tresch:
> If you think more discussion is useful, open a new email thread...
Happy new year everyone :-)
Thanks for stepping in - I think it would be nice to just scan the open
jira tickets as not all are in the right place.
Apart from that any help is apprec
Am 18.12.18 um 18:16 schrieb Aaron Coburn:
> Hi,
> I think someone with admin rights will need to cancel the current Jenkins
> build for the extensions repository. It's been stuck since 12/15:
>
> https://builds.apache.org/job/Tamaya-Extensions-Master/
DONE -
let's see if the next build terminat
Hi,
pls feel free to merge/review my first PR via Github ;-)
https://github.com/apache/incubator-tamaya/pull/29
You need to follow basic setup via gitbox.apache.org before everything
works so smoothly .
as I'm not quite sure about the correct syntax of the link I'll continue
with the other r
1 - 100 of 533 matches
Mail list logo