| Re: [nebula-dev] Nebula Build |
I think the confusion is that none of the Nebula widgets have really christened a 1.0 release yet. There are no formal guarantees on API compatibility until we go 1.0. So I don't think its so much that we're lax on API but that we are slow on development ;) We haven't gotten to a real 1.0 yet. I think all the widgets web pages still state either ALPHA or BETA. Granted, its probably another thing we aren't very obvious about.There doesn't appear to be a way to express "no guarantees" using the Eclipse versioning conventions, so using zero would be a Nebula quirk. Frankly, I don't think any other projects are this lax about API compatibility. I thought this would be an easy hack to bypass the version checking during build. It's also reasonably clear that no formal release has been made yet. I hope that our widgets will all move to a 1.0 release soon, but I don't think anyone is ready to commit to that yet. I don't have a strong objection to starting with 1.0, as long as the minor version gets incremented when an API change is made. During the development cycle, it doesn't make sense to update any version qualifiers. When we release 1.0 versions, and therefore start guaranteeing API, then we should start doing this. I see what you mean. Sounds like it would be helpful to developers using the widgets and just need easy access to new versions.I would have found this convenient a few months ago. Back then, I didn't have access to external CVS servers through my company's firewall, so I had to constantly re-download and extract the jars for each widget. An update site would make this a lot easier. The main reason to do it would be to allow other Eclipse projects to consume Nebula widgets, though. It's also a requirement for the coordinated releases. We need enthusiasm! So I may have a different opinion on some points but your enthusiasm is greatly appreciated! I'm excited that someone else is willing to help out with these project-wide things. So far I've had trouble keeping up. Right. We'll just need to do a good job of timing the releases of the different widgets, or excluding them. But you're right. We have a whole year to plan for it.I actually think it will be fairly easy for us to participate, since our projects tend to be very small and have light dependencies. If we follow the conventions, we can ride the coattails of the more complex projects and use their build tools. Of course, we'd have to get the widgets up to some standard of "release quality", but we have a year to do that. If any of the widgets are still not ready for prime time by then, we can exclude those specific plugins/features from the release. -- Peter Regards, -Chris |