Gerrit v3 and roadmap

[Artem Kazakov]

Hello all, 

In some youtube video I saw that v3 in the works, but no official information when it can be expected and what the feature set could be. 

The thing I'm particularly interested in is running gerrit with 100% git only backend, no DB. 

What is the plan for gerrit v3? 

Is there a public roadmap?

Thank you,

Artem

[Markus Duft]

Would be interested in this too, any information from the maintainers? :)

[Shawn Pearce]

Historically we don't publish much of a roadmap because what happens is based on what people contribute, and we don't have control over that as maintainers. :)

I can tell you two things Google is interested in and is working on:

- notedb

This is removing the SQL database and storing metadata in Git, with search indexes in Lucene. When its complete we will probably call that shipping version Gerrit 3.0 because of the radical change in review metadata storage.

- Refreshed UI

We are evaluating the concept of refreshing the UI using Polymer. Polymer isn't set in stone, but its something being explored and some experiments are being attempted internally. We'll see where this project goes. If its viable and making progress, we'll start showing the work externally and see if others want to help contribute.

FWIW, refreshed UI won't cause a "Gerrit 3" numbering.

[Markus Duft]

Hey,

Thanks for the Info :) Sounds promising! Are you going to be on EclipseCon Europe again? Maybe something to showcase of the new notedb already?

Cheers,

Markus

[Shawn Pearce]

On Thu, Oct 8, 2015 at 10:12 AM, Markus Duft <duft....@gmail.com> wrote:

Hey,

Thanks for the Info :) Sounds promising! Are you going to be on EclipseCon Europe again?

No, unfortunately I can't make it this year.

[luca.mi...@gmail.com]

Hi Shawn,

and what about the EclipseCon USA in March 2016 - Washington?

Luca

Sent from my iPhone

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Shawn Pearce]

Might try to make that...

[Bassem Rabil]

What about Gerrit 2.12 release ? There is no yet release candidate for 2.12. Is there a planned content to be delivered in 2.12 ? 

Or this will be discussed and addressed during the user summit and hackathon ?

Thanks

Bassem

[luca.mi...@gmail.com]

Would be best to create the stable-2.12 branch before the hackathon, otherwise it could become a release just too big !

What's missing to release 2.12? Can we put together a todo list?

Luca 

Sent from my iPhone

[Edwin Kempin]

2015-10-15 21:16 GMT+02:00 <luca.mi...@gmail.com>:

Would be best to create the stable-2.12 branch before the hackathon,

+1

 

otherwise it could become a release just too big !

What's missing to release 2.12?

We need a maintainer that has time to drive the 2.12 release...

 

Can we put together a todo list?

In the issue tracker the 'Blocking-2.12' label is already configured. We should use it to mark things we need for 2.12.

Edwin Kempin

Software Engineer

eke...@google.com

+16502534437

Google Germany GmbH

Dienerstraße 12

80331 München

Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle

Registergericht und -nummer: Hamburg, HRB 86891

Sitz der Gesellschaft: Hamburg

Diese E-Mail ist vertraulich. Wenn Sie nicht der richtige Adressat sind, leiten Sie diese bitte nicht weiter, informieren Sie den Absender und löschen Sie die E-Mail und alle Anhänge. Vielen Dank.

      

This e-mail is confidential. If you are not the right addressee please do not forward it, please inform the sender, and please erase this e-mail including any attachments. Thanks.

[Bassem Rabil]

On Friday, October 16, 2015 at 3:57:21 AM UTC-4, Edwin Kempin wrote:

2015-10-15 21:16 GMT+02:00 <luca.mi...@gmail.com>:

Would be best to create the stable-2.12 branch before the hackathon,

+1

 

+1 

Currently we have 1550+ commits on master that will be included in 2.12. 

[David Pursehouse]

OK, so after discussion among the maintainers we've decided to start
putting together the release notes and make the rc0 before the user
summit/hackathon. Here's a tentative list of the main things that we
expect to be included:

- Submit whole topic / "submitted together"
- Signed pushes
- Preferences in git (see [1] and related changes)
- Fix for broken 'related changes' tab (see issue 3416 [2])

I'll be updating the release notes within the coming week based on
what's already merged. If there's anything else pending review that
should be included, reply here and/or rebase/ping the change on
gerrit-review. For items in the issue tracker, add the Blocking-2.12 label.

Note: these features are NOT likely to be ready in time:

- Elasticsearch
- Notes DB

[1] https://gerrit-review.googlesource.com/#/c/71042/
[2] https://code.google.com/p/gerrit/issues/detail?id=3416

On 10/19/2015 09:52 PM, Bassem Rabil wrote:
>
>
> On Friday, October 16, 2015 at 3:57:21 AM UTC-4, Edwin Kempin wrote:
>
>
>

> 2015-10-15 21:16 GMT+02:00 <luca.mi...@gmail.com <javascript:>>:

>
> Would be best to create the stable-2.12 branch before the hackathon,
>
> +1
>
> +1
> Currently we have 1550+ commits on master that will be included in 2.12.
>
> otherwise it could become a release just too big !
>
> What's missing to release 2.12?
>
> We need a maintainer that has time to drive the 2.12 release...
>
> Can we put together a todo list?
>
> In the issue tracker the 'Blocking-2.12' label is already
> configured. We should use it to mark things we need for 2.12.
>
>
> Luca
>
> Sent from my iPhone
>
> On 15 Oct 2015, at 20:13, Bassem Rabil

>>> <https://groups.google.com/d/optout>.

>>
>>
>> --
>> --
>> To unsubscribe, email repo-discuss...@googlegroups.com

>> <javascript:>

>> More info at http://groups.google.com/group/repo-discuss?hl=en
>> <http://groups.google.com/group/repo-discuss?hl=en>
>>
>> ---
>> You received this message because you are subscribed to the
>> Google Groups "Repo and Gerrit Discussion" group.
>> To unsubscribe from this group and stop receiving emails from
>> it, send an email to repo-discuss...@googlegroups.com

>> <javascript:>.

>> For more options, visit https://groups.google.com/d/optout

>> <https://groups.google.com/d/optout>.
>
> --
> --
> To unsubscribe, email repo-discuss...@googlegroups.com <javascript:>

> More info at http://groups.google.com/group/repo-discuss?hl=en
> <http://groups.google.com/group/repo-discuss?hl=en>
>
> ---
> You received this message because you are subscribed to the
> Google Groups "Repo and Gerrit Discussion" group.
> To unsubscribe from this group and stop receiving emails from

> it, send an email to repo-discuss...@googlegroups.com <javascript:>.

> For more options, visit https://groups.google.com/d/optout

> <https://groups.google.com/d/optout>.
>
>
> Edwin Kempin
>
> Software Engineer
>
> eke...@google.com <javascript:>
>
> +16502534437

>
> Google Germany GmbH
>
> Dienerstraße 12
>
> 80331 München
>

> *
> *

>
> Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle
>
> Registergericht und -nummer: Hamburg, HRB 86891
>
> Sitz der Gesellschaft: Hamburg
>

> *
> *

>
> Diese E-Mail ist vertraulich. Wenn Sie nicht der richtige Adressat
> sind, leiten Sie diese bitte nicht weiter, informieren Sie den
> Absender und löschen Sie die E-Mail und alle Anhänge. Vielen Dank.
>
> This e-mail is confidential. If you are not the right addressee
> please do not forward it, please inform the sender, and please erase
> this e-mail including any attachments. Thanks.
>

> --
> --
> To unsubscribe, email repo-discuss...@googlegroups.com
> More info at http://groups.google.com/group/repo-discuss?hl=en
>
> ---
> You received this message because you are subscribed to the Google
> Groups "Repo and Gerrit Discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to repo-discuss...@googlegroups.com

> <mailto:repo-discuss...@googlegroups.com>.

[luca.mi...@gmail.com]

+1

Sent from my iPhone

[Luca Milanesio]

> On 20 Oct 2015, at 07:21, David Pursehouse <david.pu...@sonymobile.com> wrote:
>

> OK, so after discussion among the maintainers we've decided to start putting together the release notes and make the rc0 before the user summit/hackathon. Here's a tentative list of the main things that we expect to be included:
>
> - Submit whole topic / "submitted together"
> - Signed pushes
> - Preferences in git (see [1] and related changes)
> - Fix for broken 'related changes' tab (see issue 3416 [2])
>
> I'll be updating the release notes within the coming week based on what's already merged. If there's anything else pending review that should be included, reply here and/or rebase/ping the change on gerrit-review. For items in the issue tracker, add the Blocking-2.12 label.
>
> Note: these features are NOT likely to be ready in time:
>
> - Elasticsearch
> - Notes DB

*IF* NotesDB is targeted for the next release … shall we name it 3.0 ?
Getting rid of the DBMS is a *huge* step forward and deserves a major version number increase I guess ;-)

Luca.

[Dave Borowitz]

On Tue, Oct 20, 2015 at 5:50 AM, Luca Milanesio <luca.mi...@gmail.com> wrote:

> On 20 Oct 2015, at 07:21, David Pursehouse <david.pu...@sonymobile.com> wrote:
>
> OK, so after discussion among the maintainers we've decided to start putting together the release notes and make the rc0 before the user summit/hackathon.  Here's a tentative list of the main things that we expect to be included:
>
> - Submit whole topic / "submitted together"
> - Signed pushes
> - Preferences in git (see [1] and related changes)
> - Fix for broken 'related changes' tab (see issue 3416 [2])
>
> I'll be updating the release notes within the coming week based on what's already merged.  If there's anything else pending review that should be included, reply here and/or rebase/ping the change on gerrit-review.  For items in the issue tracker, add the Blocking-2.12 label.
>
> Note: these features are NOT likely to be ready in time:
>
> - Elasticsearch
> - Notes DB

*IF* NotesDB is targeted for the next release … shall we name it 3.0 ?
Getting rid of the DBMS is a *huge* step forward and deserves a major version number increase I guess ;-)

Yes, that's pretty much the definition of 3.0 :)

 

Luca.

For more options, visit https://groups.google.com/d/optout.

[Doug Kelly]

On Tuesday, October 20, 2015 at 9:40:00 AM UTC-5, Dave Borowitz wrote:

On Tue, Oct 20, 2015 at 5:50 AM, Luca Milanesio <luca.mi...@gmail.com> wrote:

> On 20 Oct 2015, at 07:21, David Pursehouse <david.pu...@sonymobile.com> wrote:
>
> OK, so after discussion among the maintainers we've decided to start putting together the release notes and make the rc0 before the user summit/hackathon.  Here's a tentative list of the main things that we expect to be included:
>
> - Submit whole topic / "submitted together"
> - Signed pushes
> - Preferences in git (see [1] and related changes)
> - Fix for broken 'related changes' tab (see issue 3416 [2])
>
> I'll be updating the release notes within the coming week based on what's already merged.  If there's anything else pending review that should be included, reply here and/or rebase/ping the change on gerrit-review.  For items in the issue tracker, add the Blocking-2.12 label.
>
> Note: these features are NOT likely to be ready in time:
>
> - Elasticsearch
> - Notes DB

*IF* NotesDB is targeted for the next release … shall we name it 3.0 ?
Getting rid of the DBMS is a *huge* step forward and deserves a major version number increase I guess ;-)

Yes, that's pretty much the definition of 3.0 :)

This is just my opinion, but it might be easier for $DAYJOB to swallow one last release before moving everyone to NotesDB anyway. Personally, I am excited to see NotesDB in practice, but I worry there will be significant contention on that upgrade (and concern over its reliability/performance).  If we get a 2.12, we probably won't be looking at 3.0 until this time next year anyway.