Mailinglist Archive: opensuse-project (422 mails)
| < Previous | Next > |
Re: [opensuse-project] Announcing openSUSE Tumbleweed project
- From: Greg KH <gregkh@xxxxxxx>
- Date: Wed, 1 Dec 2010 14:05:43 -0800
- Message-id: <20101201220543.GA21590@xxxxxxx>
On Wed, Dec 01, 2010 at 09:18:57AM +0100, Vincent Untz wrote:
I don't see "contributors" having to do any different work here. They
should be creating packages for Factory today, which is where the
packages for Tumbleweed will come from, just after that same contributor
deems them "stable" enough.
I totally do not understand your question here, care to rephrase it?
"people" can choose which repo to use, that's not going to hurt anyone
here. "contributors" will still have the same workflow as before, just
that they might get pinged every once in a while if their package should
be sent to Tumbleweed or not.
It's really not much of a difference at all for contributors, but the
benifits for our users are quite high, if they want to use this type of
rolling distro (as many have said they would like to do.)
thanks,
greg k-h
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
Le mardi 30 novembre 2010, à 23:24 +0100, Pascal Bleser a écrit :
On 2010-11-30 09:11:04 (-0800), Greg KH <gregkh@xxxxxxx> wrote:
There's been many discussions over the past years about a "rolling[...]
update" version of openSUSE on lots of different mailing lists and in
person a different conferences.
So the time now is to stop talking about it, and actually trying to do
it :)
So, any thoughts, ideas, objections?
Excellent idea!
Just needs to be filled with manpower now ;)
:-)
One other thing I'm worried about is that this might result in some
contributors focusing on the rolling update, and some others focusing on
the "usual" release. Ideally, people would work together, and on both,
but that's "ideally", and things will be different. So that literally
splits our effort.
I don't see "contributors" having to do any different work here. They
should be creating packages for Factory today, which is where the
packages for Tumbleweed will come from, just after that same contributor
deems them "stable" enough.
This of course means something from a manpower perspective, but there's
a bigger risk in divergence: code/technical divergence, but also
community divergence.
On the other hand, I do understand that we probably want something with
low overhead when it comes to submitting a change.
So how should we do things? Can we require that all changes going in one
will go to the other in some way too? Or do we need a model that is
similar to Debian's one?
I totally do not understand your question here, care to rephrase it?
To summarize, I don't want people to have to choose between our current
way and the rolling release way -- if they do have to choose, they'll
just go "oh well, I don't care about the other" and we'll be losing
something.
"people" can choose which repo to use, that's not going to hurt anyone
here. "contributors" will still have the same workflow as before, just
that they might get pinged every once in a while if their package should
be sent to Tumbleweed or not.
It's really not much of a difference at all for contributors, but the
benifits for our users are quite high, if they want to use this type of
rolling distro (as many have said they would like to do.)
thanks,
greg k-h
--
To unsubscribe, e-mail: opensuse-project+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-project+help@xxxxxxxxxxxx
| < Previous | Next > |