Thoughts on Fedora Server lifecycle

[Kevin Fenzi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

ok, so I finally sat down and looked at this some more... 

But I'm still not sure I understand what you are proposing. ;) 

Assuming base is releasing every 6 months, we make a 1.0pr1 against f21
base, then a 1.0pr2 against f22 base, then a final 1.0 against f23
base. 

How is server 1.1 made? Do we not need to make security updates or
other changes to base? Or we only take the f23 base and use it for the
rest of 1.x's life? 

What repo(s) does server use in this model? 

We wouldn't be releasing a 1.0 version for 12 months? I think thats the
opposite of 'agile' ;) 

Also, I am not liking the release after base idea. We already 'freeze'
for releases so we can get everything in a testable state. If we do so,
then release base, it becomes a moving target so regressions can land
when we are trying to test server. 

I don't think we can do a increased lifecycle unless base also supports
that personally. 

I have some alternate ideas, will post in another thread. ;) 

kevin

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBCgAGBQJSfRAOAAoJEEs3sNgP+7te69kP/2tl0SjtupcsC8kb0KJrFo1x
X6uAS/QIlAXCH4yvC2mjvMQHmSDlpAdG/cq4Nyzq/d2XZQm15W53qNIut0QZm1oB
x5NckfGZKlz3AA4IJdzJq9mtGqpNRQj+ELenFrayzCTxiEZgxX64pG9rVxeaSpxx
8mytkaOEqVw56hAiAht7QMBp2MwA9kyt2+msLVMGqie9OfbkX3fJ2KW3MIYtlz5g
TeZFyAUKd0w9o5Dwqb6lVXtg3O686y/dPcy6AlK2pyxBuB+ODOw445ggmFi/Ddko
0O5Pc9b9frCl5CewlHKUr1gjvDMLDXLy14W+VRtIx4zM7I+RG97RCbmb5/T7DYMj
lP1RuMPM4KDF7AOorNsvBV8acMGNo9ol3nOj5Z3e2SpiRV7r82qsoNyuVGeWEbZU
z1htiH4H8MXTi7/wqIhwysCJe8CixuzDdTQk0iMudNcj6/ymX3Xb23+f/C+BK5aq
v3d4UzNtIj97h/ZMNGWfc/wF+Szdk2bczFz6qrMOvaYv6IJvbSRmKDFdVRuaBEog
y+yhrttKJi6pW54GeV+vsybucuaj+kUyQ5E9g7zc1fm4b536JaMMhn8neHBAU806
qOs0uOtVm6Jt7yUuWucHMW6hVxVewdB9YFuG72vUqoJXksamzB0wYZnStwXCJuZa
Alh/e7nvjcAfA8ChlmV+
=yfDD
-----END PGP SIGNATURE-----