i dont see how you expect to get traction when people know there are big api breaks coming soon? why try something that will be completely broken in a week?
We're not making this build for new people to try out.
the people who are interested are the people who build from source
Yes, like us. And like I said, before I want to start working on the last few breaks, I'd like to take a breath and have a version without the breaks of which i know it works well, so that while I'm upgrading and testing in the background, the rest of the team can go on and we can make a deployment with it. I'm sure this would be appreciated by more people who currently work on 1.3.
, so i dont see any reason to create any publically accessible artifact.
What are you afraid of? Eelco
