The release of v0.1.0

[fukamachi]

@snmsts @guicho271828 @KeenS

I think the first version of CL21 should be released as soon as possible.
Do you have any concerns so far?

[snmsts]

I think purpose of the first release are nothing technical, but political.
I don't have any concern,so far.
But, Release is some kind of fix.I think we need to establish how the incompatible change are introduced in the future and also should clarify how users avoid that kind of mess in practical.

[KeenS]

Before v0.1 comes, I want to finish these discussions: #4 #35 . If you think these are settled, I have no concerns.

[fukamachi]

I don't think v0.1.0 is so serious thing. It is an alpha release for telling early adopters CL21 is going ahead.

I don't recommend to use CL21 v0.1.0 for serious use. Though it would not be dynamic one, the specification probably will be changed. Backward compatibility isn't guaranteed.

After the release of v0.1.0, these things in my mind.

• Send a request for adding CL21 to Quicklisp
• Asking people to write standard libraries of CL21 in CL21
• No dynamic changes until v0.2.0

And, the development process should be changed. Sending a pull request for each changes may be a better habit.

I think we need to establish how the incompatible change are introduced in the future and also should clarify how users avoid that kind of mess in practical.

I think ASDF's version-specifier is the only way to avoid incompatibility. I know it is not enough, though.

http://common-lisp.net/project/asdf/asdf/The-defsystem-grammar.html

[snmsts]

I think we could have package nicknames like :cl21/0.1 and by *features* to take care.
This is just an idea and I don't think We should do it right now at all.

[fukamachi]

Too heavy... Let's do it when the first stable release.

[snmsts]

:) let's consider when time is come.

[fukamachi]

@guicho271828 @m-n @snmsts @EuAndreh @KeenS

Hi CL21 contributors,

I'm thinking to change the license of CL21 before the first release.
Its license is MIT currently, but, if you really think that it can stimulate the next generation of Common Lisp, its license should be more free license like Public Domain.
I hope that other people who want to create another next generation of Lisp would reference CL21 and would reuse it.

There's your code in it, so I cannot change it without all your approval.
Please answer if it's okay whether if you agree or disagree with this.

[KeenS]

I agree.

[m-n]

You have my approval.

[snmsts]

No problem.

[EuAndreh]

Sure, no problem.

[guicho271828]

okay and take care yourself.