[
https://issues.apache.org/jira/browse/FELIX-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388495#comment-17388495
]
Steven Huypens commented on FELIX-6440:
---
https://github.com/apache/felix-dev/pull/8
ponziani opened a new pull request #82:
URL: https://github.com/apache/felix-dev/pull/82
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsub
Steven Huypens created FELIX-6440:
-
Summary: Delegate JettyConfig properties to OSGi LogService
Key: FELIX-6440
URL: https://issues.apache.org/jira/browse/FELIX-6440
Project: Felix
Issue Type
While fixing a few problems with the new downloads page I found some with
Atomos.
The old download page is incorrect, as it links to one of the atomos binary
bundles but the only required links, to the source archives, are broken.
I fixed that problem on the new downloads page, so the tar.gz an
I believe the release area at https://www.apache.org/dist/felix has the latest
release of every Felix subproject, and the download page lists most of them. I
think that having a project represented in “releases” and on the download page
implies that it’s maintained and that problems will be add
The new version of that page,
https://felix.staged.apache.org/documentation/subprojects.html, still has links
to the GitHub README. If we stick with this (my 3rd option) we should at least
also have links in the nav.
I suspect that it’s not clear how my preferred solution would work or look.
Am 27.07.2021 um 10:59 schrieb Bertrand Delacretaz:
On Tue, Jul 27, 2021 at 10:50 AM Carsten Ziegeler wrote:
...I prefer having the docs of a subproject directly within git as this
makes updates that involve code and docs much easier (a single PR)...
I also like that option as long as all
On Tue, Jul 27, 2021 at 10:50 AM Carsten Ziegeler wrote:
> ...I prefer having the docs of a subproject directly within git as this
> makes updates that involve code and docs much easier (a single PR)...
I also like that option as long as all modules are discoverable from
the main website.
For Sl
I think this is a tough one. It seems today people using github expect
the documentation to be part of the git repo in the form of a readme. It
also seems that having the docs side by side with the code helps in
keeping them in sync.
On the other hand having the docs as part of our website add
+1
And thanks to all the great work and effort you put into this, David! I
think we all owe you something now :)
Regards
Carsten
Am 26.07.2021 um 21:39 schrieb David Jencks:
I’ve:
- added a link to the KEYS file and validation instructions to the downloads
page.
- updated the site-how-to a
+1
regards,
Karl
On Tuesday, July 27, 2021, Raymond Augé
wrote:
> +1
>
> Ray
>
> On Mon., Jul. 26, 2021, 3:39 p.m. David Jencks,
> wrote:
>
> > I’ve:
> >
> > - added a link to the KEYS file and validation instructions to the
> > downloads page.
> > - updated the site-how-to and release-manage
11 matches
Mail list logo