I'm +1 for a top level sandbox repo. Anyone should be able create a
project in that.
Once the project graduates out of the sandbox we should create a top level
On Wed, Jan 13, 2021, 11:30 AM Anshum Gupta wrote:
> Building this as a branch is an option, but building it outside in a
> personal
On Wed, 13 Jan, 2021, 6:00 am Anshum Gupta, wrote:
> Building this as a branch is an option, but building it outside in a
> personal repo is exactly what's not the Apache Way.
>
Negative. Nothing of that is mentioned in
https://www.apache.org/theapacheway/. Private decision making isn't
Building this as a branch is an option, but building it outside in a
personal repo is exactly what's not the Apache Way.
Code should be designed and built in the Apache world, else it'd be a
grant/donation and not really a PR. Also, you can't create a PR against a
repo that doesn't exist
I feel this is placing the cart before the horse.
We can always build this as a branch or a repo under your own account.
Once we reach a point where the project is reasonably mature, you can
create a repo and contribute it upstream.
On Wed, Jan 13, 2021 at 6:27 AM Anshum Gupta wrote:
>
> I
Wish you a very happy new year, Namgyu!
Please proceed, thanks!
On Wed, 13 Jan, 2021, 1:01 am Namgyu Kim, wrote:
> Hi Ishan,
> It's late, but *happy new year*!
>
> There is a blocker issue for 8.x (including 8.8)
> https://issues.apache.org/jira/browse/LUCENE-9661
>
> Would it be okay to
Hi Ishan,
It's late, but *happy new year*!
There is a blocker issue for 8.x (including 8.8)
https://issues.apache.org/jira/browse/LUCENE-9661
Would it be okay to cherry-pick the commit for LUCENE-9661 to the 8.8
branch after merging?
On Wed, Jan 13, 2021 at 1:48 AM Ishan Chattopadhyaya <
I understand what you are saying, which is also my reason to not have a
mono-repo. This way it's easier to manage and drop a repository when it's
not needed. It doesn't cause clutter and lives in isolation.
I think we are on the same page in terms of the intention.
On Tue, Jan 12, 2021 at 10:51
Look at the branches that are cluttering up our main repository, many
symbolic of unfinished work. If we start one repo each for everything we
hope to finish, we'll make Solr annoying in a new way.
There is no reason multiple artifacts can't be released independently from
the same repo. Why are
Thank you everyone!
I'll move forward with the cross-dc repo creation then as mentioned in the
original email :)
If we want to change the approach on the repo, we can always change that
before we release anything in the future.
On Mon, Jan 11, 2021 at 10:32 AM Mike Drob wrote:
> I'm seeing
Hey all,
Two follow ups on recent discussion.
I reviewed the gc/ref-counting part of the BlobDirectory proposal on
SOLR-15051 that David mentioned. We talked about it a bit offline and
agreed that while an automatic gc mechanism is really needed for what
he's trying to do, the requirements of
Please go for it if you think it won't disrupt the stability and can be
wrapped up in 2-3 days.
On Tue, 12 Jan, 2021, 10:08 pm Walter Underwood,
wrote:
> I’d love for SOLR-15056 to be in, but it is just a patch now and hasn’t
> had anything besides
> local testing, so that is a bit of a long
I’d love for SOLR-15056 to be in, but it is just a patch now and hasn’t had
anything besides
local testing, so that is a bit of a long shot.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Jan 11, 2021, at 9:29 AM, Timothy Potter wrote:
>
> 15036
12 matches
Mail list logo
