Have been asking for it for a while ;) obviously +1.
Be aware that Jenkinsfile.full post-merge will probably fail because, at
the very least, the FreeBSD hosts won't have fdb and can't run docker to
containerise it. This will need some exploration to resolve but
shouldn't be a blocker.
The
+1. Thanks for starting this, Paul. I was actually going to try and
drive this a month or two ago, but things got busy for me.
I'd also support renaming it to 'trunk' but really don't care what we pick.
The first commercial version control system I used to use, called that
branch "main":
+1
This conversation kind of spilled into the other thread about merging,
so I replied there as well about main vs master and rebasing. Sorry
about the confusion.
On Wed, Sep 9, 2020 at 2:05 PM Robert Samuel Newson wrote:
>
> I'm +1 in favour of renaming to 'main'.
>
>
>
> > On 9 Sep 2020, at
Agree that its time to get the fdb-layer work into master, that's where couchdb
4.0 should be being created.
thanks for preserving the imported ebtree history.
> On 9 Sep 2020, at 17:28, Paul Davis wrote:
>
> The merge on this turned out to be a lot more straightforward so I
> think its
I'm +1 in favour of renaming to 'main'.
> On 9 Sep 2020, at 18:26, Alessio 'Blaster' Biancalana
> wrote:
>
> I'm not against nor in favor :-D
> Words matter but in my opinion git's master was never _that_ master.
> Anyway, if it bothers someone... let's do this!
>
> Concerning open PRs, I
Agree that its time to get the fdb-layer work into master, that's where couchdb
4.0 should be being created.
thanks for preserving the imported ebtree history.
> On 9 Sep 2020, at 17:28, Paul Davis wrote:
>
> The merge on this turned out to be a lot more straightforward so I
> think its
Nice :)
> On 9 Sep 2020, at 18:32, Nick Vatamaniuc wrote:
>
> That looks really nice, Jan. Thanks for sharing!
>
> On Wed, Sep 9, 2020 at 1:29 PM Alessio 'Blaster' Biancalana
> wrote:
>>
>> Wow, that's _amazing_. I'm glad seeing this kind of effort in an ecosystem
>> like the one of CouchDB,
That looks really nice, Jan. Thanks for sharing!
On Wed, Sep 9, 2020 at 1:29 PM Alessio 'Blaster' Biancalana
wrote:
>
> Wow, that's _amazing_. I'm glad seeing this kind of effort in an ecosystem
> like the one of CouchDB, cool stuff!
>
> Alessio
>
> On Wed, Sep 9, 2020 at 6:03 PM Jan Lehnardt
Wow, that's _amazing_. I'm glad seeing this kind of effort in an ecosystem
like the one of CouchDB, cool stuff!
Alessio
On Wed, Sep 9, 2020 at 6:03 PM Jan Lehnardt wrote:
> Dear CouchDB Community,
>
> I’m happy to announce Opservatory https://opservatory.app, my company
> Neighbourhoodie’s
I'm not against nor in favor :-D
Words matter but in my opinion git's master was never _that_ master.
Anyway, if it bothers someone... let's do this!
Concerning open PRs, I don't know, I think original authors can easily
rebase. Also, the next release will cut some stuff open I think, so maybe
Congratulations on the launch, Jan.
On 9 September 2020 9:33:26 pm IST, Jan Lehnardt wrote:
>Dear CouchDB Community,
>
>I’m happy to announce Opservatory https://opservatory.app, my company
>Neighbourhoodie’s latest product for monitoring your CouchDB instances.
>
>Opservatory knows CouchDB
Could we rename prototype/fdb-layer to main and it will be the base of
4.x? There might be a few things we could bring in from master into
main like elixir test improvements, tooling, but it would be a smaller
diff than bringing everything from prototype/fdb-layer into master.
Then master can be
Alexander,
Any PRs that aren't trivially rebased against the current
prototype/fdb-layer will by definition break regardless of what we
call our default branch moving forward.
Paul
On Wed, Sep 9, 2020 at 11:11 AM Jan Lehnardt wrote:
>
> I’m in favour and I think the FDB merge is a nice
The merge on this turned out to be a lot more straightforward so I
think its probably the way to go. I've got a failing test in
couch_views_active_tasks_test but it appears to be flaky rather than a
merge error. I'll work though getting `make check` to complete and
then send another update.
I’m in favour and I think the FDB merge is a nice opportunity to take
the plunge.
Best
Jan
—
> On 9. Sep 2020, at 17:40, Paul Davis wrote:
>
> Howdy Folks!
>
> Words matter. I've just started a thread on merging all of the
> FoundationDB work into mainline development and thought this would be
This obviously will break all the current PR to master branch just because
of naming. Is it worth this?
What problems renaming will solve? And why does that suddenly become
important?
--
,,,^..^,,,
On Wed, Sep 9, 2020 at 6:40 PM Paul Davis
wrote:
> Howdy Folks!
>
> Words matter. I've just
Dear CouchDB Community,
I’m happy to announce Opservatory https://opservatory.app, my company
Neighbourhoodie’s latest product for monitoring your CouchDB instances.
Opservatory knows CouchDB better than any single human could. We’ve put
our combined multi-decade experience with supporting
Howdy Folks!
Words matter. I've just started a thread on merging all of the
FoundationDB work into mainline development and thought this would be
a good time to bring up a separate discussion on renaming our default
branch.
Personally, I've got a few projects where I used `main` for the
mainline
Howdy folks!
I've just gone through a rebase of `prototype/fdb-layer` against
master. Its not quite finished because the ebtree import went wrong
during rebase due to a weirdness of the history.
I have a PR up for the rebase into master for people to look at [1].
Although the more important
19 matches
Mail list logo
