Re: [seam-dev] Seam JIRA for Seam 3
I've had some questions on IRC, with my proposals inline:
Q: How are we going to do do release versioning? Will all modules in a seam release have
the same version number?
No, modules will be free to have different versions. We need to discuss the version number
scheme too. I suggest that the main Seam releases are simply version 3.x.0 (no
micro-version-number, unless we need a bug fix release). Modules should follow the
standard scheme of incrementing the minor number if they had significant featuers/break
APIs, and otherwise change the micro-version-number. The major version number
shouldn't change.
Q: Will it be "simultaneous release" once a year like eclipse does?
No, firstly a simultaneous release implies that each module does it's major feature
updates at the same time, I don't see we need to stick to that. Instead we will bundle
a set of compatible modules. Secondly, we aim to release more than once a year :-)
Q : How will this work with Maven? Won't it be annoying for developers to have to
explicitly specify which module to depend on (and update this every time a Seam bundle
comes out)?
We'll provide a so called "stack POM" [1], which users can import into their
project. They then just bump the Seam version number:
<dependency>
<groupId>org.jboss.seam</groupId>
<artifactId>seam-bom</artifactId>
<version>3.0.2.CR1</version>
<type>pom</type>
<scope>import</scope>
</dependency>
On 10 Mar 2010, at 11:57, Pete Muir wrote:
All,
As we split Seam into modules (and as some like remoting and XML approach a beta
release), we need to consider how JIRA should look for Seam 3.
We plan to release modules independently, with a "feature-boxed" lifecycle,
releasing modules either as features are added, or critical issues arrive. We also plan a
"bundle release" at regular intervals, which takes all the modules, and provides
a single stack that are tested to work well together.
Keeping JIRA simple and monolithic has the advantage of being easy to understand and
point people at. We can use components to track a module. We would have to prefix the
version with the module name, and tracking issues to releases becomes pretty difficult.
Using a JIRA project for each module allows much cleaner tracking of issues to releases.
I favour the latter, but am interested in others opinions.
Pete
_______________________________________________
seam-dev mailing list
seam-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev