Mailinglist Archive: opensuse-project (207 mails)

< Previous Next >
[opensuse-project] Re: Code names
  • From: Jim Henderson <hendersj@xxxxxxxxx>
  • Date: Wed, 6 May 2009 22:30:02 +0000 (UTC)
  • Message-id: <gtt31a$3iv$1@xxxxxxxxxxxxx>
On Thu, 07 May 2009 08:13:29 +1000, Mark V wrote:

Problem is that end dates can change as development on the next release
progresses.  Wasn't there recently a shift from a 6 month development
cycle to an 8 month development cycle?

No problem. During development the release name can be used and only
tagged with an EOL date during the release candidate phase (for example)
- assuming you are correct in saying that the EOL date is as fluid
during the dev cycle as you suggest it is.

My experience (not in OSS but in closed-source development) is that the
cycles can and do vary.

That's why a product like NetWare has an EOL that's 15 years in the
future (was at one point for current releases).

Suppose in 2 years it's decided to go to a 10-month development cycle?
That shifts the end dates for the ones that are already out there.

What! Now I am worried, is it really the case that the openSUSE
end-of-life date changes once the 'final' is released? This seems nuts
to me so would appreciate some unambiguous clarification.....

Bear in mind that I'm speaking from the perspective of working at a
software company where EOL dates typically are dependent on the next
product release.

It seems to me that it's a better idea to go with something that isn't
able to change rather than something that may.

Thanks for brining this to my attention. I had no idea that the EOL date
could change once the final release was made.

Now you're just being facetious. ;-)


Jim Henderson
Please keep on-topic replies on the list so everyone benefits

To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups