NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO toi meme!!! :P
I'm sorry, but I don't want to release a 0.95.1 release without release
0.95! and I don't want to release both at the same time...
we're not confusing ANYBODY, and we're not fucking anything, we can't
make
a NEW release if there wasn't any before...
All we did is 'tag' the release in CVS, but the 0.95 release was never
OUT!!!!
let me find an analogy, it's like when you 'want to go to mcDonals', you
go out and once you get there, you say "hey, there's a XXXXX restaurant
in
front of mcDo's I'll go there".. then, are you forced to get to mcDo
before going to the other restaurant ? would you say that you're not
hungry anymore because you 'though of going to mcDo' even if you didn't
go
there ? no.. it's the same thing here (sorry for the worst analogy I
ever
made :P) we wanted to release 0.95, we tagged cvs (similar to going out
until we reach mcdo) but we never released 0.95 (didn't enter mcdo), so
we
can release 0.95 with the latest CVS now without any worries because
noone
knows about it!
anyways... we may talk about it later on msn, I'm tired now...
what do other devels think ?
KaKaRoTo
On Sat, 10 Dec 2005 13:48:44 -0500, Jérôme Gagnon-Voyer
<[EMAIL PROTECTED]> wrote:
> NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
>
> 0.95 is done we said it.
> 0.95.1 is the next release.
>
> We tag a NEW release. This is to be sure we don't confuse packages.
>
> Le 05-12-10 à 13:46, Youness Alaoui a écrit :
>> no, look, 0.95 will be out, the CVS tag 0.95 isn't the final one, I
>> will retag a 0.95 and we'll create a new "0.95" release since this
>> one is hidden from everyone...
>> now the thing is, one we create the packages, we're still not going
>> to release!!! because we'll be waiting for the website...
>> now my question was, we're going to release 0.95, I'm going to tag
>> a new 0.95 (this is what Jerome called 0.95-1) and I want it to be
>> more stable with language files updated.. so I say "r we sure it's
>> ok now?" I found a few problems with webcam : if capture extension
>> is not compiled, there is no warning... the webcam isn't even
>> canceled.. but that is not critical because if it doesn't work, the
>> user will launch the wizard... and capture not compiled will not
>> exist in binary packages...
>> about languages, I'll be waiting for Harry or Hatredman to give me
>> their 'go'.
>> the pakcages will be created in time once these two issues are
>> finished (I get approval of everyone saying "yes, I think we're
>> stable", and I see no 'new' bugs in the bug system for cvs... and
>> lang maintainers tell me 'we're good here'), then either we release
>> when we get the packages ready, if Lee gives us his 'go', if not,
>> the packages will stay there and be waiting for Lee's approval once
>> the website will be finished and ready...
>> now my question was :
>> for the website, what is still remaining ? what's the status ? can
>> I get a time estimates on what's remaining to do ?
>> for stability, I do understand there's not much we can do now
>> for languages, I'd also like if possible to have a status, how many
>> languages are in the queue, and time estimates on when they will be
>> incorporated to CVS... I just updated and saw a lot of lang files
>> changin, so I guess we're almost there on this topic..
>> for packages, we'll do it as fast as we can, but I assume it will
>> take 1 day or a max of 2 days, this is my time estimates (I can
>> provide the packages in the same day, I expect Phil to do the same
>> for his rpms, and we'll just be waiting for other packagers which I
>> would like them to be as fast as we are)
