Hi,
I have been thinking lately about how we can improve our development
process for contributors/developers/release managers.
I have listed some issues that I perceived as important with proposed
solutions at
https://cwiki.apache.org/confluence/display/SLING/Scaling+Sling+Development
All comme
> To spot those stale PRs we can consider building a dashboard of open pull
> requests. Alternatively, an automated email once per week to dev@sling
> mightalso work (or might get ignored).
i think this would be very helpful. PRs often get overlooked in all the mail
traffic.
mail report would
Another challenge I've seen is trying to connect the code it github to the
documentation on the site (and visa versa). I wonder if a low effort option
would be to add a metadata field for the project(s) to link documentation
pages in github, something like:
title=Test Page
type=page
status=publi
Hi
On Wed, Mar 6, 2019 at 7:56 PM Daniel Klco wrote:
> ...I wonder if a low effort option
> would be to add a metadata field for the project(s) to link documentation
> pages in github, something like:..
...
> tags=tag1,tag2
> repos=auth-form,scripting-jsp-taglib
...
Great idea!
If we use tags f
On Thu, 2019-03-07 at 10:33 +0100, Bertrand Delacretaz wrote:
> Hi
>
> On Wed, Mar 6, 2019 at 7:56 PM Daniel Klco wrote:
> > ...I wonder if a low effort option
> > would be to add a metadata field for the project(s) to link
> > documentation
> > pages in github, something like:..
> ...
> > tags=t
On Wed, 2019-03-06 at 17:19 +, Stefan Seifert wrote:
> > To spot those stale PRs we can consider building a dashboard of
> > open pull requests. Alternatively, an automated email once per
> > week to dev@sling mightalso work (or might get ignored).
>
> i think this would be very helpful. PRs
Sorry for the late feedback, in general I really like the idea to
improve the release process!
The wiki states:
Many of these must be run by the release manager, since by definition
releases are individual acts in the Apache Software Foundation.
Isn't pushing a button in Jenkins when you
So just out of interest: Is there ASF regulation that totally forces
releases to be built on personal machines or could this in theory be
done in an CICD pipeline (if the user identity is correctly propagated
to fulfil "by definition releases are individual acts in the Apache
Software Founda
Hi Georg,
On Fri, 2019-03-29 at 22:40 +0100, Georg Henzler wrote:
> Sorry for the late feedback, in general I really like the idea to
> improve the release process!
>
> The wiki states:
>
> > Many of these must be run by the release manager, since by
> > definition
> > releases are individual
On Mon, 2019-04-01 at 14:58 +0200, Georg Henzler wrote:
> So just out of interest: Is there ASF regulation that totally forces
> releases to be built on personal machines or could this in theory be
> done in an CICD pipeline (if the user identity is correctly
> propagated
> to fulfil "by definit
Hi Robert,
thanks for clarifying!
... It's an interesting read, if you have the time.
[2] is a 94 messages thread, impressive.
The current ASF release policy is at [1], and it states that
Before casting +1 binding votes, individuals are REQUIRED to download
all signed source code packages
On Mon, 2019-04-01 at 16:11 +0200, Georg Henzler wrote:
> Hi Robert,
>
> thanks for clarifying!
>
> > ... It's an interesting read, if you have the time.
>
> [2] is a 94 messages thread, impressive.
>
>
> > The current ASF release policy is at [1], and it states that
> >
> > Before casting +1
12 matches
Mail list logo
