Re: [Iverilog-devel] Thinking of Icarus Verilog 10

[Stephen W. <st...@ic...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I've gotten generally positive feedback from this idea, so I'm
going to set a deadline for objections. If I don't hear any
objects by the evening of Saturday, 25 April 2015, I will feel
free to start wrapping up an Icarus Verilog release anytime
from the 26th on. This will involve locally testing the package
build, then making a branch and making an actual draft release.

Maybe a week after the draft release, I'll probably make the
Version 10 release (10.1) and we can start promoting the new
release to distribution packagers.

Sound like a plan?

On 04/08/2015 01:38 PM, Stephen Williams wrote:
> 
> I know this has been discussed before, but I want to bring it up 
> again. I think we are due for a new release.
> 
> I've been noting that a huge portion of users are finding that 
> their needs are met by recent snapshots that are not otherwise 
> handled by the 0.9 release. We've been spending some amount of our
> support time just telling people that "it's been fixed" in the
> master branch.
> 
> But there are many users out there who get their Icarus Verilog fix
> from package managers, and so are using the 0.9 release. These 
> people are not particularly motivated to build from source, and 
> after all they shouldn't need to. Our making a release is our way
> to say that this is what we recommend.
> 
> Since we've been recommending git master for a while now, maybe it
> is time to make a release.
> 
> Also, name change. Rather then go to 0.10.x, let's simple call it
> version 10. Somewhere along the line, Icarus Verilog became 
> production ready while we weren't looking. I think the leading zero
> is no longer informative.


- -- 
Steve Williams                "The woods are lovely, dark and deep.
steve at icarus.com           But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlUxlZgACgkQrPt1Sc2b3ilgygCfZwaCxK+dLv6fQ74DROSxF5iP
Sg4An1z0kq9UnKOmoZnazfwNTiY2SdAh
=uzVD
-----END PGP SIGNATURE-----