|
From: Martin W. <ic...@ma...> - 2020-10-11 20:24:29
|
OK, in that case we should publicise it more:
- create a release on GitHub
- upload the files to SourceForge (or put up a redirect notice
if you would rather steer people towards GitHub)
- announce on iverilog-announce (in case anyone still reads that)
- add some release notes on the Wiki
On 11/10/2020 20:28, Stephen Williams wrote:
> My intent is that 11.0 is a "release", and not a draft, but I'm OK
> with having an 11.1 release sooner rather than later. Releases may
> have versions. Note that v10 had 4 (10.0 - 10.3) and probably could
> have done with more. But within releases, vvp and the language must be
> substantially compatible, with no surprises.
>
>
> On Fri, Oct 9, 2020 at 4:22 AM Martin Whitaker
> <ic...@ma...> wrote:
>>
>> On 26/09/2020 21:59, Stephen Williams wrote:
>>> I've made an 11.0 release, and the release source files are here:
>>>
>>> <ftp://ftp.icarus.com/pub/eda/verilog/v11/>
>>>
>>> Try it out, and let's see how it goes. Feedback in this mailing list,
>>> especially with packaging issues.
>>>
>> Did you intend this to be a trial run or the final release? If the
>> former, I think it would be worth updating to pick up the fix for
>> https://github.com/steveicarus/iverilog/issues/374, which was a
>> regression w.r.t. v10.
>>
>>
>> _______________________________________________
>> Iverilog-devel mailing list
>> Ive...@li...
>> https://lists.sourceforge.net/lists/listinfo/iverilog-devel
>
>
>
|