HI,
> From what I can see with httpd, the issue is the same(?)
Not quite as I not see any release candidates listed.
Thanks,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands,
On 2/9/19 8:37 AM, Justin Mclean wrote:
Hi,
IMO either way it should be ok because
It’s not OK as it doesn’t agree with ASF release policy. You can’t provide
release candidates to the general public and call them releases.
I do see that several ASF projects seem to avoid this issue but I’m
Hi,
> IMO either way it should be ok because
It’s not OK as it doesn’t agree with ASF release policy. You can’t provide
release candidates to the general public and call them releases.
I do see that several ASF projects seem to avoid this issue but I’m not sure
how they do it. (See for
Hi,
> When I played around with maven-release-plugin today, I found out that
> Github would automatically generate the release at "
> github.com/apache/incubator-xxx/release" when we update the tag. I think
> that some projects may inadvertently create a release on Github for their
> release
I’d agree- it’s a “feature” of GitHub and I didn’t see a way to turn off
“turning a git tag into a release”
I see that there is a API to edit a release to say it is “pre-release”
https://developer.github.com/v3/repos/releases/#edit-a-release
IMO either way it should be ok because
a) the tag is
Hi all,
I'm Seunghyun who's working on the first Apache release for Pinot project.
When I played around with maven-release-plugin today, I found out that
Github would automatically generate the release at "
github.com/apache/incubator-xxx/release" when we update the tag. I think
that some
Hi Julian,
A perfect example!
I think we should add a checkbox to the podling report where the podling
indicates when they are fully in compliance with release policy. Until that is
done we don’t worry.
Additionally, Infra could tag and “release” with appropriate description when
they move a
HI,
> We allowed Druid to continue making releases outside of Apache during
> incubation because ASF releases were not possible. There were various reasons
> - they could not release from main line because IP transfer had not been
> completed (if I recall correctly), and they also needed to
If we don't want the unapproved release happens in this case, I think we should
asked them to give an exact date of joining the incubator.
The new incubator project community should know, after the proposal accepted
and with the date deadline, we don't allow to do unapproved release. And we
I’m a mentor of Druid.
We allowed Druid to continue making releases outside of Apache during
incubation because ASF releases were not possible. There were various reasons -
they could not release from main line because IP transfer had not been
completed (if I recall correctly), and they also
Hi,
One of the issues I’ve seen is that project continues to make releases in
GitHub after being accepted into the incubator, in some case is this because
the repo hasn’t been moved over yet, in other cases it’s because they believe
that the code base is not Apache ready. What should we do in
Hi,
So I just checked the next bunch of podlings to report to see if we have any
other issues with ASF releases policy and sadly we do and again it larger than
I expected. Some of these are minor issues and easily fixed, some are not. In a
couple of cases I may not of looked deeply enough into
I support move than copy too.
Move is better, not just for keeping star, fork and watch. These are also
important too.
The more important is, GitHub provides repo address auto redirect. If the user
or article links to the old repo, it will forward to the new one(Apache one)
automatically.
Hi,
> We need to make sure that pre-Apache releases whether source or binary are
> treated in a fair way.
As long are they are not in after the date of incubation and clearly marked I
see no issues.
> An über-comment - let’s be exceedingly careful with time limits for
> “compliance”.
What
On Wed, Feb 6, 2019 at 3:41 PM Justin Mclean wrote:
>
> Hi,
>
> > If projects want to make convenience binaries available for installation
> > via Docker and DockerHub, then it seems like we need an official Apache
> > DockerHub repository. Do we have one of those, or are folks just publishing
>
> On Feb 8, 2019, at 1:36 PM, Justin Mclean wrote:
>
> HI,
>
> In the thread on guidelines for distributions I suggested some common naming
> to help with trademarks, branding and be in line with release policy.
>
> There's a possible security issue here, as people could (in theory) take
HI,
In the thread on guidelines for distributions I suggested some common naming to
help with trademarks, branding and be in line with release policy.
There's a possible security issue here, as people could (in theory) take over
the old name and put something malicious there if the old name
Hi,
> - Convenience binary artifact releases need to be made from approved voted
> on approved ASF releases.
OK.
> Wait, you mean binary releases, not just source code tags?
Binary releases [1] (see step 7) and unapproved release are possible in GitHub.
Once I get some more feedback I’l put
On Fri, Feb 8, 2019 at 12:27 PM Justin Mclean
wrote:
> Hi,
>
> > This sentence is very confusing to me. If the release is "unofficial”
> then it can't be subject to ASF's policy, no?
>
> I used the word unofficial as some of these artefacts are connivance
> binaries. I and don’t want to open up
> On Feb 7, 2019, at 1:52 PM, Dave Fisher wrote:
>
>
>
>> On Feb 7, 2019, at 1:44 PM, Craig Russell wrote:
[snip]
>>
>> Larger discussion: Is there a reason for projects coming into incubation to
>> have the old repository moved (i.e. renamed) instead of being copied? I
>> cannot think
Hi,
> This sentence is very confusing to me. If the release is "unofficial” then it
> can't be subject to ASF's policy, no?
I used the word unofficial as some of these artefacts are connivance binaries.
I and don’t want to open up the “we only release source" can of worms.
> I am actually not
Great effort getting it all documented! Would really love to see this
converge ASAP.
On Thu, Feb 7, 2019 at 11:08 PM Justin Mclean
wrote:
> Hi,
>
> Feedback welcome. If you think anything here is not in line with the ASF
> release and distribution policy please speak up. Currently it’s not
Sign me up (
Am 08.02.19, 11:55 schrieb "Lars Francke" :
One more thing: We've got three mentors. If anyone else would like to
volunteer we won't say no :)
I've used the E-Mail addresses from your mails in the proposal. Feel free
to update to an @apache.org address if you
One more thing: We've got three mentors. If anyone else would like to
volunteer we won't say no :)
I've used the E-Mail addresses from your mails in the proposal. Feel free
to update to an @apache.org address if you want to.
On Fri, Feb 8, 2019 at 11:05 AM Lars Francke wrote:
> Thanks to the
Thanks to the three of you.
Those arguments make sense to me and we indeed have a few "newcomers" with
us (that includes me in a non-committer role) so I've changed my opinion
and think the Incubator way would be the best.
I'll edit the Wiki proposal (and add Christofer whom I've forgotten,
My initial thought was: this should go straight to TLP: Training should be
done by people who know what they're training about: whether it be the
Apache Way or a specific project. All the committers will likely be people
who've at least reached committer status in a project, and most of them
will
> Gesendet: Freitag, 08. Februar 2019 um 04:58 Uhr
> Von: "Dave Fisher"
> An: general@incubator.apache.org
> Betreff: Re: Tying Dockerhub into development and release management
[...]
> > On Feb 7, 2019, at 7:51 PM, Chris Lambertus wrote:
[...]
> >> On Feb 7, 2019, at 6:47 PM, Justin Mclean
Hi,
after spending some time thinking about this I also tend towards the
Incubator route as I am sure this will help build and grow an active
community and processes.
Best regards,
Sönke
On Fri, Feb 8, 2019 at 6:38 AM Justin Mclean wrote:
>
> Hi,
>
> > discussion seems to have died down.
Hi Antoine,
First of all: thank you for the LinkedIn accept.
More information about the PNS (Podling Name Search) can be found via [1].
After having yourself familiarised with that, I suggest to register a JIRA
ticket with project 'PODLING NAME SEARCH' for the new project name, see
[2]. I
also
29 matches
Mail list logo
