Getting to 1.0 release

[DerekP]

I would like to start thinking seriously about a time line for a 1.0 release of Delve. I do not have a solid date in mind, however my current goal is to have a 1.0 version of Delve ready before the end of the year.

What does a 1.0 release look like?

* Support for Windows (work already being done)
* Support for 32 bit Linux systems
* Improved variable setting (thanks Alessandro for kicking this feature off)
* Watchpoint command (https://github.com/derekparker/delve/issues/279)
* Fix OSX test flickers
* More... just look at 1.0 milestone in GitHub: https://github.com/derekparker/delve/milestones/1.0

What does a 1.0 release mean?

Essentially a 1.0 release means that we are locking down the API for external clients, locking down subcommand / interactive commands (we can add, but not remove / rename / etc..), and finally providing a release of the software we assert to be viable for daily use. I have thought about committing to support certain versions of Go, but that's a bit flaky right now as there are very likely to be upstream patches to Go that either Delve devs or Go core devs will need to make based upon the needs of Delve (improved Dwarf info, etc..).

How do we get there?

Over the next week or so I will create issues for any outstanding 1.0 issue that does not have one, and will be working off the 1.0 milestone in GitHub to knock things out. If you are a current contributor or potential contributor that list is the best place to look for work that needs to be done that would provide the most value to the project. Aside from that, ongoing overall stability patches are appreciated.

Major blockers

The only major blocker I see is dealing with the Go release cycle as there are issues that need to be fixed regarding the Dwarf output specifically that will improve the debugging experience. I will be working to help write patches to fix these issues, and also coordinate with the Go team to try and get these issues addressed, ideally before the Go 1.6 code freeze.

We need input

Input from users and folks writing software that integrates with Delve is extremely important, especially for integrations as 1.0 will be a locked down API. Please continue to provide feedback either on this list or through issues. If there is anything not on the 1.0 release schedule that you as a user or integrator would like to see, please raise an issue.

If everything goes as planned we will have a 1.0 release before the end of this year. Huge thanks to all contributors for the great work.

[Florin Patan]

Hi Derek,

First of all thank you and all the contributors for this project.

Now, for the 1.0 release.

I'd rather say this would be a welcomed thing but, in the light of the Go 1.6 release date which should be around Feb 1st, wouldn't it be better to release delve 1.0 then?

The reason for this is that you say there should be some changes done in Go to help delve out and I guess that releasing delve 1.0 with Go 1.6+ support as the official supported Go version (even if it will have the beta label) would make things much more simpler and easier on the side of maintenance and bug reports.

Also, I'd rather try and see what other features should we expect from later releases of Delve so that we know that the API will be able to incorporate those easily.

I'll update more on this as soon as I have more input, meanwhile, I'll try to spread the word to more users so that they can help out with testing and so on.

Kind regards,

Florin

[DerekP]

Hey Florin,

That's a good point, perhaps it would be better to announce an official 1.0 release around the time of 1.6. Maybe it would be better to work on this timeline:

End of year: Official beta release
Jan 2016: Fix beta bugs, new beta or RC release
Feb 2016 (aligned with Go 1.6 release): Official 1.0 release

The official beta release should support everything NOT dependant on Go patches. Once we officially release 1.0, state that the officially supported version of Go begins at 1.6, and we can maintain supported versions from there as we see fit.

Thoughts?

[Arpit jaswani]

Hello Derek,

I have been looking for dlv support for 32 bit arch systems, seems like it was planned to release years back.
Still are there any plans to release? or you have dropped the idea because of no demands?

[Arpit Jaswani]

Sorry, I forgot to mention the platform.
I was looking for windows platform.

Any plans on that?

[alessandr...@gmail.com]

Support for linux/386 was added recently, adding windows/386 is probably
easy to do. But nobody is currently working on it, AFAIK.

> --
> You received this message because you are subscribed to the Google Groups "delve-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to delve-dev+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/delve-dev/611324da-c840-45e6-a360-21ad57991128%40googlegroups.com.
>

[Arpit Jaswani]

I would like to get hands on that, can i get into it?
if yes, are there any key guidelines from i need to start or which part should i work on, to make it work  for windows/386.

On Thursday, 2 April 2020 14:59:57 UTC+5:30, alessandro.arzilli wrote:

Support for linux/386 was added recently, adding windows/386 is probably
easy to do. But nobody is currently working on it, AFAIK.

On Wed, 01 Apr 2020 22:47:30 -0700, Arpit Jaswani <jaswan...@gmail.com> wrote:
> Sorry, I forgot to mention the platform.
> I was looking for windows platform.
>
> Any plans on that?
>
> --
> You received this message because you are subscribed to the Google Groups "delve-dev" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to delv...@googlegroups.com.

[chainhelen]

In fact, I am doing this but just the beginning.

But recently I lost my job again because of the company's economic downturn which cause I have no continuous time to complete. 

You can reference https://github.com/go-delve/delve/pull/1884 and https://github.com/go-delve/delve/pulls?q=is%3Apr+is%3Aclosed+arm if you want to get into it.  

Hope those can help you, thx.

在 2020年4月3日星期五 UTC+8上午2:10:07，Arpit Jaswani写道：

[Arpit Jaswani]

Hi,

I am going trough the same situation, at a point i decided to upgrade my old machine.
But i would give it a try, let's see if we could hack it.
Thanks for the guidance.

[chainhelen]

Hi, are you still doing it on windows/386?

在 2020年4月4日星期六 UTC+8上午12:16:47，Arpit Jaswani写道：