On Mon, 21 Mar 2005 10:11:15 -0600, Sasvata (Shash) Chatterjee <[EMAIL PROTECTED]> wrote:
> >I'd like to see the 1.2 release out by the end of May at least. > > > Let's get the list defined. I can start working on it right away, and > based on who else can support the efforts, we can see where we come out. Sounds good. Can you publish the list of what needs release in conjunction with Fortress 1.2? Alternatively you could also make the list a JIRA issue under Excalibur Fortress. > Although more documentation is always nice, do we need to hold up a > release for that? > If we have less documentation than we had for Fortress-1.1, then > certainly, that would be a reason to hold the release. Perhaps not hold up the release completely, but we cannot ignore the lack of tutorials and documentation. Initially I want to do a couple quick "getting started" tutorials in the wiki for Fortress 1.2. > The binary "platform" is a good thing to get people up and running. > What are the plans for the platform in terms of what it needs to do? There isn't a feature list yet. Basically it's just a zip/tar that someone can download that includes all the other jars necessary for getting started and a simple hello world app. If there are more feature requests, we should get them into JIRA. I already have the initial code for the platform distro in svn. > I would love to see Eclipse .classpath/.projects included in SVN and > maybe even in src distributions. I'm using Eclipse more now myself and I'd like to make the build more Eclipse friendly. Preferrably, I'd like it if the eclipse .project and .classpath files could be created via the maven plugin. We'd need to adjust how some of the projects pick up the root project.xml. > That's always a plus. Do you mean that Fortress lists dependencies > unnecessarily (i.e. those are listed in the POM, but not referenced in > code)? > Or, that we could make some simple changes to eliminate some > dependencies we really have? If changes, I'd say, let's get 1.2 out and > do the code changes later. I think we should be able to make more of them optional. What does everyone else think about requirements for a 1.2 release? -- jaaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
