Still this doesn't solve the problem I face with building on top of Jini
where I need something to say as Seven/Service/Product is compliant with
Jini version x.y
Long discussion I suppose :)
Any other opinions from committers and folks on the list?
I'm for the start simple and evolve as we go along approach.
- For River's temporary version number AR1 seems fine.
- We may decide at some point that there is a need for multiple projects
- then so be it (from briefly looking at Avalon, it seems that they
split up into sub-projects later on in life - people with a grasp of
Apache project history please correct me). I'm expecting that the
development process at Apache can accommodate such a change.
- For bugtraq id's I prefer a custom field.
- I don't really have a strong preference for having a JTSK prefix in
the version numbers or not. If asked to choose, I would go with no
prefix - as Mark suggested there is some value in being able to just
refer to the old version numbers and dealing with river as a progression
from the JTSK. As for potential confusion for newbies, that could be
fixed with a brief history of river (the bugtraq id field will also be a
hint that this came from the JTSK).
thanks -Jim
