Quoting from the document -
Unique Enough Names
The name needs be unique enough to avoid confusion with software that
already exists. For the community to be able to protect its reputation for
quality and openness, its name needs to unique enough to have potential as
a trademark.
But this isn’t
Hi Justin,
The download page of SINGA is (
https://singa.incubator.apache.org/en/downloads.html ). The page that you
mentioned is the index page. The official ASF releases are in the downloads
page.
The index page is the landing page of the website and it contains all the
different ways to get
Noted. Thanks, Justin!
Regards,
Wei
On Tue, Feb 19, 2019 at 4:04 PM Justin Mclean
wrote:
> Hi,
>
> > Can you please elaborate on release policy issues with Singa ?
> > I checked a few things but couldn't find the issue.
>
>
> Nothing too major. If you look at the download page [1] it’s
Hi,
> Can you please elaborate on release policy issues with Singa ?
> I checked a few things but couldn't find the issue.
Nothing too major. If you look at the download page [1] it’s encouraging people
to use docker [2] and AWS [3]. Both pages probably has some minor
branding/trademark
Hi Justin,
Can you please elaborate on release policy issues with Singa ?
I checked a few things but couldn't find the issue.
Thanks,
Thejas
On Fri, Feb 8, 2019 at 5:51 PM Justin Mclean
wrote:
> Hi,
>
> So I just checked the next bunch of podlings to report to see if we have
> any other
Thx Justin, I was assuming the community just simply creating tag in the
github and have not published them as releases.
Will need to review what had been create there
- Henry
On Fri, Feb 15, 2019, 2:02 PM Justin Mclean Hi,
>
> > Will be following up with the community of DLab to make sure
Hi,
> Will be following up with the community of DLab to make sure they follow
> the ASF release policy.
Thanks Henry I assume you saw the different GitHub repos and noted the dates of
“releases" there?
Thanks,
Justin
-
To
Hi Justin,
Will be following up with the community of DLab to make sure they follow
the ASF release policy.
Thanks,
- Henry
On Fri, Feb 8, 2019 at 4:51 PM Justin Mclean
wrote:
> Hi,
>
> So I just checked the next bunch of podlings to report to see if we have
> any other issues with ASF
Hello Justin,
Could you please tell us about issues with ASF release policy in Marvin?
Thanks!
Yifei Zhang
Em seg, 11 de fev de 2019 às 02:27, Kenneth Knowles
escreveu:
> [1] https://issues.apache.org/jira/browse/LEGAL-438
>
> :-)
>
> Kenn
>
> On Sun, Feb 10, 2019 at 1:06 PM Justin Mclean
>
[1] https://issues.apache.org/jira/browse/LEGAL-438
:-)
Kenn
On Sun, Feb 10, 2019 at 1:06 PM Justin Mclean
wrote:
> Hi,
>
> > It sounds like httpd has the same problem since some of these listed
> > “releases” are failed vote attempts (and so not official releases)
>
> Yep it is and to try
Hi,
> It sounds like httpd has the same problem since some of these listed
> “releases” are failed vote attempts (and so not official releases)
Yep it is and to try and sort it out I’ve raised a ticket with legal. [1] Until
that is resolved just carry on the best you can.
> What are our
... so I think we need to provide an option here.
No question that any unauthorized release is not allowed. But what about
while voting for a release?
It sounds like httpd has the same problem since some of these listed
“releases” are failed vote attempts (and so not official releases)
>From a
On 2/9/19 9:38 AM, Makoto Yui wrote:
Justin,
Could you please tell us what
issues exist in Hivemall?
I'd also be interested in knowing (you may use dev@ or private@ as you
see fit) what issues exist with pony mail and release policies :)
Thanks,
Makoto
2019年2月9日(土) 9:51 Justin Mclean
Justin,
Could you please tell us what
issues exist in Hivemall?
Thanks,
Makoto
2019年2月9日(土) 9:51 Justin Mclean :
>
> 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
On 2/9/19 8:50 AM, Justin Mclean wrote:
HI,
From what I can see with httpd, the issue is the same(?)
Not quite as I not see any release candidates listed.
ah, well, httpd doesn't do release candidates :p we tag a release, vote
on it, if it fails, you burn the version number and use a new
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
To: general
Subject: Re: Podlings not following ASF release policy
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
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
26 matches
Mail list logo
