Just some thoughts on this thread.
1. Any 1.4 or 1.3.x release should always be API compatible. So we
should never break public API here.
2. I would prefer that any schema changes and any serialization of
classes also remain binary compatible. Again, avoids migration and
upgrade issues.
3. I'm all for maintenance releases being every couple of months, but I
also think it is good to plan for a 1.4 release in either 6 months or a
year. Maintenance releases should occur at least 3 or 4 times a year,
minor version releases a little bit longer out.
4. If we plan to do this, it would be nice to have some Milestone
releases periodically before getting to the Release canidates or
maintenance releases. Allows for testing purposes.
5. Ideally I'd like to see one Build system choosen as the Master
build. I know we have adopters that use buildr and some that use maven,
but maintaining two build systems isn't productive long term.
6. During the maintenance of code and any 1.4 release, ideally I'd like
to see one unit test framework settled upon. Since the majority is
junit, I think it would be a good idea as we fix other bugs and features
to slowly migrate all the tests to junit 4 style. Makes it easier to
get started and test regardless of ide or if you are running tests via
the build scripts.
That's all I can think of at the moment.
Dave
On 06/18/2010 03:30 AM, Rafal Rusin wrote:
On Fri, Jun 18, 2010 at 11:48 AM, Jeff Yu<[email protected]> wrote:
I was thinking about 2 months release with 2 weeks forking (code freeze with
that branch). ;-)
OK, it's fine.
Regards
jeff
On Fri, Jun 18, 2010 at 6:54 PM, Rafal Rusin<[email protected]> wrote:
I would prefer to release 1.3.5 and then 1.4.0.
I'm fine with 1.3.5 as soon as there are running maven axis2-war tests
in hudson.
And I agree - we should release regularly. Something like every 2
months with 1 month forking period (beta release).
So we can plan 1.3.5 fork on 15-th July and release on 15-th August
(along with 1.4 fork).
On Fri, Jun 18, 2010 at 6:00 AM, Jeff Yu<[email protected]> wrote:
Hi team,
Since we've released the 1.3.4, I am thinking about our roadmap for the
next
release.
Firstly, I'd think that it is better that we have a release plan like 1
release in 2 months at least, could be just a bug fix release, or a
feature
enhancement, as long as we have something to deliver,
don't want us to be in the position that have 1 release in 6 months. ;),
what do you think of this? we should create a wiki page to state whats
the
tentative release date for our next release, and whats the feature or it
is
just a bug fix release over there.
Secondly, as we discussed on the other thread with regard to the jpa
refactoring table renaming, we thought it is better that we did this on
1.4
release, as for 1.3.x series, we shouldn't expect to have big impact on
the
database schema change,
in this case, would be for the OpenJPA users.
So here is the question, what is our next release? 1.3.5 or 1.4?
Let me know what do you think of this.
--
Cheers,
Jeff Yu
----------------
blog: http://jeff.familyyu.net
--
Regards,
Rafał Rusin
http://rrusin.blogspot.com
--
Cheers,
Jeff Yu
----------------
blog: http://jeff.familyyu.net
