Release cadence

48 views
Skip to first unread message

Michael Andre Pearce

unread,
Jul 4, 2017, 1:18:21 AM7/4/17
to Registry
Hi All,

Though mostly looking at Satish and Harsha on this :)

As we have a lot of features to add still, and there will always be just the next PR or feature needed. 

Would it be best to maybe have a monthly release for the project.

This way users get regular releases they can rely on, to which we get more feedback of features needed, and we don't end up holding a release for some new feature, as it simply will just if completed be a month away.

Thoughts?

Cheers,
Mike

Harsha Ch

unread,
Jul 4, 2017, 10:22:49 AM7/4/17
to Michael Andre Pearce, Registry
Agree. We have a pending 0.3 release of registry and I'll be starting the release thread in two days for that. This is based on already tagged branch. We can follow that up with new features thats addede recently in about 3-4 weeks.
Thanks,
Harsha

--
You received this message because you are subscribed to the Google Groups "Registry" group.
To unsubscribe from this group and stop receiving emails from it, send an email to registry+u...@googlegroups.com.
To post to this group, send email to regi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/registry/0a59628b-a5ad-4837-a8f1-c1a0c0a5a5ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Michael Andre Pearce

unread,
Oct 12, 2017, 11:37:08 PM10/12/17
to Registry
Hey Harsha and Satish,

On the note of keeping a release cadence.

It's been almost 3 months now since last community release, there's been a lot of work on schema management (thanks Satish)  is it worth thinking to clean up any open ends, and start a release?

Cheers
Mike

Harsha Ch

unread,
Oct 13, 2017, 12:07:38 PM10/13/17
to Registry, Michael Andre Pearce
+1 on doing a release.

Thanks,
Harsha

Satish Duggana

unread,
Oct 13, 2017, 8:54:24 PM10/13/17
to Harsha Ch, Registry, Michael Andre Pearce

We can target release by Nov 1st week with pending items

 

and cleaning any other loose ends (as mentioned by Michael).

 

Michael,

Can you file issues for any loose ends that you find?

 

Thanks,

Satish.

Michael Andre Pearce

unread,
Oct 19, 2017, 9:37:44 PM10/19/17
to Registry
I think we caught most of the ones (fixes) for confluent api during the reviews of the recent PR that was made.

I have a kafka connect piece, to contribute at some time, but this is new feature, so shouldn't hold release for.

Like wise i have a JMS support feature i would like to contribute (i have this in my own github and the org i work for uses this already), but have a problem copyrighting that to hortonworks, i raised a discussion point about what is the timeline to going to apache incubator, as that would make it more feasible for me to contribute that,again this is non blocker for release. 

Also we would possibly have a c++ client ready in about 6 months time, but similar copyright issue, which wouldn't be an issue if handing copyright to open source foundation.

Harsha Ch

unread,
Oct 20, 2017, 1:05:12 AM10/20/17
to Registry, Michael Andre Pearce
Hi Michael,
            Thanks for continued support and contributions to Registry. Currently we’ve plans on integrating Hive Metastore ( take this out of hive project) and Registry into one project. This has been the goal to have a single registry/metastore to serve the schemas for data in motion and data at rest.  Looks like you are interested in such merge as well based on this https://github.com/hortonworks/registry/issues/158 . We are working towards this goal and at least get a beta version out in Jan. This will be proposed as the Apache project soon after.  Let me know if you’ve any questions regarding this.

Thanks,
Harsha

Michael Andre Pearce

unread,
Oct 31, 2017, 4:31:16 AM10/31/17
to Registry
Hi Harsha,

I think it be good to keep registry able to be deployed as a standalone product. As one of its main uses is as a direct replacement for Confluent's SR.

What sort of timescales you looking at?

On another note for the next release, I know we said 1st Nov, on Friday 27th Oct we hit an issue, I'm looking into it, but essentially atm, it looks like because we cannot tell client side between an issue cause by not being able to talk to SchemaRegistry vs an actual Avro payload issue as all get wrapped into just one single exception class, meaning app teams cannot work out to discard (corrupt binary) vs retry (schema registry is simply down)

Could i ask for a stay of a few days? To allow us to develop a possible solution and PR it?

Cheers
Mike

Satish Duggana

unread,
Oct 31, 2017, 4:36:42 AM10/31/17
to Michael Andre Pearce, Registry

Hi Mike,

No problem, we can wait for few more days to get your fixes merged.

 

Thanks,

Satish.

Michael Andre Pearce

unread,
Oct 31, 2017, 4:37:07 AM10/31/17
to Registry
FYI, id love to come on board as part of the team if it does get into incubation at apache, I'm a committer on apache activemq project already (michaelpearce at apache dot com).

Michael Andre Pearce

unread,
Oct 31, 2017, 4:54:33 AM10/31/17
to Registry
Thanks Satish.

Michael Andre Pearce

unread,
Oct 31, 2017, 5:16:34 AM10/31/17
to Registry

Michael Andre Pearce

unread,
Oct 31, 2017, 5:17:14 AM10/31/17
to Registry
dot org (obviously ;) - doh! moment) 

Harsha Ch

unread,
Oct 31, 2017, 9:51:55 AM10/31/17
to Registry, Michael Andre Pearce
Hi Michael,
                You’ll be part of committers when we incubate it in Apache. Regarding running just the schema registry we can do this via config options. I’ll share the repo details.
Thanks,
Harsha

Michael Andre Pearce

unread,
Nov 2, 2017, 2:53:08 AM11/2/17
to Registry
Hi Satish and Harsha,

I have opened a PR for review, on the issue i have raised a question (as a comment) id like some input for the direction to take to handle something.

Cheers
Mike


On Tuesday, 31 October 2017 08:36:42 UTC, Satish wrote:

Satish Duggana

unread,
Nov 2, 2017, 4:39:46 AM11/2/17
to Michael Andre Pearce, Registry

Hi Michael,

I will review by EOD tomorrow.

prashant...@gmail.com

unread,
Nov 15, 2017, 11:21:12 PM11/15/17
to Registry
Hello,

Do we have an ETA for the next release?

Satish Duggana

unread,
Nov 16, 2017, 3:50:53 AM11/16/17
to prashant...@gmail.com, Registry

Hi,

Can we wait till these two issues are merged? I am also fine to have release with current master, we can have maint release in next few weeks addressing below issues.

 

https://github.com/hortonworks/registry/issues/298

https://github.com/hortonworks/registry/issues/302

 

Thanks,

Satish.

prashant...@gmail.com

unread,
Nov 16, 2017, 10:23:55 AM11/16/17
to Registry
Hi Satish,

I like the idea of doing a maint release few week down the road. That said, there seems to be a fix available for https://github.com/hortonworks/registry/issues/298 already. I am using 0.3.0 release and would really like to get the new release which adds the ability to delete schemas.

Thanks,
Prashant

prashant...@gmail.com

unread,
Nov 19, 2017, 2:04:09 PM11/19/17
to Registry
Hi Satish,

Any update on doing a release ? 

Thanks,
Prashant

Satish Duggana

unread,
Nov 20, 2017, 3:34:43 AM11/20/17
to prashant...@gmail.com, Registry

Hi,

I was holding on that to finish https://github.com/hortonworks/registry/issues/302 before the release. It will take few more days to complete that. So, we will add that in subsequent maint release.

 

I will start release process tomorrow with current master branch.

Reply all
Reply to author
Forward
0 new messages