On Mon, Apr 11, 2011 at 5:21 PM, Drew Adams <Druonysus@aol.com> wrote:
On Monday, April 11, 2011 01:08:42 PM you wrote:
On Mon, Apr 11, 2011 at 3:44 PM, Drew Adams <Druonysus@aol.com> wrote:
On Monday, April 11, 2011 09:32:35 AM Kim Leyendecker wrote:
Am 11.04.2011 11:13, schrieb Rajko M.:
This may not be a problem at home where you have thick download pipe and hours to do installation and updates, but at friends site shorter is better. You come with patched DVD and in one hour you are done, including first steps how to use. No distribution offers this now, and as they don't have OBS they will need some time to catch up.
Well, this can you have with *SUSE Studio*. Just download the latest packages, create your own repository or load the rpms on a archive up and tick them for being used for your appliance. Then you create a live CD/DVD and go to your friend and install it there.
I don´t see any problem in this thanks
PS: Just a suggestion: Test the appliance in a virtual machine and _then_ go to the friend and install it there.
So in other-words Kim... this is something that is easy to do? If so, it makes the point that, if it is so easy to do, why would we not implement this idea so the community can benafit from someone going through the process you outlined. Would there be a better way other than that to achive this idea with KIWI or any other tool to streamline the process? -- Drew Adams
I have openSUSE on several servers. I never even consider upgrading them in the first 2 months of a release, so I certainly understand the difference between the day zero release and a day 60 release + updates.
And for server use, I don't like even the window of time between performing a baseline upgrade and when I get the patches applied.
So, I for one like the idea of doing at a minimum a major release every 8-months and a sub-release 2 months later.
But I'd be happy with:
11.4 - March '11 11.4.1 - May '11 12.1 - Nov '11 12.1.1 - Dec '12
etc.
And if that could be handled with minimal manpower, I for one would find myself keeping "x.x.1" releases in my physical archives, but tossing the x.x releases.
So while I like the basic idea Drew has a lot, I'd like to keep to exactly the current numbering for "major releases" and add a 3rd digit for sub-releases.
Greg
Greg,
I think that sounds like a fine implementation of the idea as well... especially since there seem to be some that really like the other numbering that was decided upon before my proposal. I do think that if we were to only do one patched "sub-release" it should be 4 months after the major release. This way it would be in the middle of our 8 month cycle and would include more patches... but either way is good. -- Drew Adams
Drew, In this do-ocracy, I think only the numbering needs to be agreed upon now. Then anytime someone actually creates a sub-release it gets the next sub-release version number. So if tomorrow someone creates, 11.4.1, then it is done. All that is needed is to track the sub-releases on the wiki and have a place for people to download them. If then 2 months from now, another sub-release is done, it gets 11.4.2. Thus, the schedule is not preset, and a new sub-release can be made whenever the people doing the work feel is the right time. For me in general, I would wait to upgrade a server until a sub-release came out out that had at least a couple months of patches in it. But I'm just one user and I'm not volunteering to create the sub-releases. Whoever does the work gets to set the timing. Greg -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org