On Tuesday 12 March 2002 07:02 am, Geoffrey Talvola wrote:
> What _I_ find confusing is that every component of Webware has its
> own independent release number, while Webware as a whole _also_ has a
> release number.  It makes cutting a release much more difficult (and
> obviously despite my efforts I didn't catch some of the release
> numbers when I cut 0.7b1), and just confuses people.  I honestly
> can't remember any time when someone on the mailing list actually
> referred to, for example, the MiddleKit release number.
>
> Why not axe all of the separate release numbers and just give the
> entirety of Webware one release number?
>
> Chuck?

Yeah, I find that to be a headache as well. But one concern is that the 
quality level between components can vary (alpha, beta, production), so 
I'd still like to retain some kind of quality indicator that would show 
up in the component index.

Also, I'd still like to have release notes for the components. How do 
we match those up? Would a component in its second revision just get a 
RelNotes-0.8 for example? Would the version of the component package be 
0.8 and 0.2?

Perhaps most of the problems would go away if we either didn't refer to 
the version numbers in the non-release notes docs (such as User's 
Guides), or those were updated upon installation. That's actually where 
I have the most trouble.

-Chuck

_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel

Reply via email to