On Thu, 17 Nov 2005 10:10:01 -0500, Arieh Schneier
<[EMAIL PROTECTED]> wrote:
* I want to release 0.95 NOW :
Jerome
Youness
Karol Krizka
Harry
Fred
Alvaro
* No, we keep the way we had before, release 0.95RC1, then RC2, then
... and
0.96 for next year... (hoping we finish what has been pending for
0.95RC1)
-------------------------------------------------------------------------
------
* I want user's opinions
Youness
Karol Krizka
* No, we'll take the vote from the developpers as being the ultimate
decision.
Harry
Alvaro (I think the user opinion is clear!)
I don't have time now, but probably wont have time tomorrow to write
anything so I will make it short.
I am not adding my name to these lists as I believe the options are
flawed
in the understandings, it appears that the 2 options have been combined
into
1. Releasing 0.95 now means we release what we have as a complete stable
release and then start working on 0.96. The second option is to release a
0.95 candidate and hold off new features until it has had a chance to be
cleaned of any minor bugs that shouldn't have to wait till 0.96. Now I
think
we should release a 0.95 candidate and fix any bugs reported before
starting
to work on 0.96, I also think that is what Karol wanted before Youness
explained the options and 'combined' them into 1.
Ok, I guess I wasn't clear enough on both possibilities.. the first one is
we release 0.95 now, start working on new features, bug fixes, and when we
think that our 0.95TODO is completed and almost all bugs known were fixed,
we release a "more stable release" of 0.95 (with bug fixes AND new
features if any were added since the 0.95 release)...
The second choice is "we keep it as it is now" which means that we will
continue waiting for the 0.95RC TODO to be finished (webcam assistant is
the one I'm thinking about now...) THEN we release 0.95RC1 (it doesn't
mean now...) then once it's out, we'll work on the pending issues only,
until we get the whole 0.95 TODO completed without adding new features..
I'm actually asking to go into an anarchy instead of an democracy... (I
don't want it to be a dictature either).. so these are my 2 choices... and
I chose the anarchy... to "just get it out and fix it later" because I
think we're never gonna release anything if we keep it like this...
If still uncertain, I can try and explain how the 2 options are not the
same..
Whether we call the
release 0.95RC1 followed by 0.95 or 0.95 followed by 0.95.1 is
irrelevant,
as long as the users know this is stable but still has some minor bugs
that
we want reported so that we can release a new patched release with no
extra
features.
Well, changing the build number doesn't mean it has only bug fixes, it
means it has minor fixes... so 0.95.1 can have new features and bug fixes
for 0.95 while 0.95RC1 means it's a release candidate, it means "we're not
yet into the 0.95 state" and it means that we're only waiting for bugs to
come in and the 0.95 release will only be bug fixes of the RC.. That's why
I said 0.95->0.95.1 instead of 0.95RC1->0.95
Whatever we call it 0.95 or 0.95RC1 shouldn't matter, as long as 0.94
recognises it as a new update. We can then correct the code to recognise
the
next release correctly (before releasing this 1). So what I am proposing
is
new options:
Well, as I just said, it's not that irrelevant because of the implied
meaning of each release, but it's not important and we don't really care
about that, and as you said, as long as 0.94 reconizes both releases as
"newer" and the next release to be out should have a fix in order to
reconize later versions correctly..
* (1) I want to release 0.95 now but hold off on new features until we
have
had a chance to fix any bugs that get reported (notifying users that
there
may be some and we want them to report it - after checking the known
issues
page..):
- Arieh
* (2) I want to release 0.95 as a stable build and start working on 0.96
immediately:
- Youness..
The reason is because the 0.95 is not going to be released because we
finished our TODO, it's because the development has stalled.. I think
noone is motivated now because there is a feature freeze.. if we remove
the feature freeze, we'll all (those who have time) get motivated again
and we'll work on amsn and at the same time, fix those bugs that were
pending for a year...
I answere 2, even if it says "start working on 0.96".. I think it should
be "start working on the next release" whether it's 0.96 with all it's
milestones, TODO list, etc... or just next release being 0.95.1 with a few
new features and bug fixes, or whatever.. as long as we can say to
everybody "do whatever you want now"
/////////////////////////////////
Then a second question for those that chose (1) above;
* (a) I want this release to be called 0.95RC1 then followed by 0.95:
* (b) I want this release to be called 0.95 then followed by 0.95.1 etc
- Youness
* (c) I want this release to be called 0.95.1 then followed by 0.95.2 etc
* (d) I don't really care as long as the check for new update is
checked/fixed to work with what is chose:
-Arieh
Further comments:
Arieh - I chose (d) as it doesn't matter to me, but out of the first 3 I
would probably choose (c) if I was forced to make a choice. As long as we
ensure that users were notified on amsn main page, and maybe even on the
download page, that this release may contain some bugs but we endeavour
to
release a new version with just bug fixes and no extra features as soon
as
the bugs have been found and eradicated.
I chose b because I don't want the RC releae as discussed earlier and I
don't like releasing a 0.95.1 without a prior 0.95.0... But other than
that, it could be "b" or "c", I don't really care, as you said, as long as
it updated correctly.
Thanks for sharing your opinion...
btw, you didn't answer, do you think we should get users involved in a
poll ?
p.s.: I did intend to make it clear to users that there are a few bugs and
"here's the list of known bugs in this release" and they should not yell
at us if it eats their pc :)
--
KaKaRoTo
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Amsn-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/amsn-devel
