Zooko wrote:
* I would know that a new stable, tested, release of darcs is going to come
out within about X months.
* I would know that if I am using darcs version 1.a.b that I can upgrade to
darcs version 1.a.b+e and get no interface changes, no added features, no
performance
Tommy Pettersson wrote:
On Tue, Feb 28, 2006 at 09:13:35PM -0800, Jason Dagit wrote:
Perhaps we could even do something like once every X months there is a
feature freeze. During the feature freeze the unstable repo is handed
to Tommy for Y days (or weeks) where only bug fixes are
[snipsnip]
I'd like to know what you think of this idea.
I'm not totally against these ideas, but I do wonder what the purpose is.
I understand the purpose when there is a large project, with many developers,
so that they can plan. But darcs is a smaller project. Most of the submissions
are
I'm definitely not trying to say that there is no value in having a
more strict release schedule, but I myself do not see a big need. Perhaps
you could explain why it would be helpful? In more specific terms than just
saying we could plan around releases.
Specifically what I was thinking
[EMAIL PROTECTED] wrote:
Since I mostly imagine this being a feature of use to other people (including
to my clients and co-workers) rather than for myself, I think I'll fall silent
on this issue and let other people have their say.
I agree with Zooko. I've come to expect that bumps in the
Zooko,
What you're basically suggesting is the creation of a new ``critical
bug fixes only'' branch at every release. That's not a bad idea, but
such a branch would need a maintainer.
Your other suggestion is that Tommy commit to a fixed schedule of
releases, rather than following his current
On 3/4/06, Olivier Thauvin [EMAIL PROTECTED] wrote:
Le Jeudi 02 Mars 2006 02:01, Tommy Pettersson a écrit: But I wouldn't mind the more common major.minor.bugfix.PostgreSQL use major.minor.bugfix|improvements
If major or/and minor change, this mean internal schema has changed and youneed to
On Tue, Feb 28, 2006 at 08:08:18PM -0600, Erik Schnetter wrote:
On Feb 28, 2006, at 19:06:09, Tommy Pettersson wrote:
Without much surprise, here comes darcs 1.0.6, very much
It seems to me that this new version identifies itself as
1.0.7pre1, not as 1.0.6. Is this an error in my setup, or
Without much surprise, here comes darcs 1.0.6, very much
identical to 1.0.6rc1.
Important bugfixes:
* Fix bug in Get --tag that produced a corrupt repository (issue67, Edwin
Thomson).
* Revert optimization that sometimes applied patches incorrectly and
corrupted the repository. This
On 3/1/06, Tommy Pettersson [EMAIL PROTECTED] wrote:
Without much surprise, here comes darcs 1.0.6, very muchidentical to 1.0.6rc1.snip
New features:lots of new nice feautures presentedI just have a question about the versioning number. Given all the great new features added to darcs in this
On 2/28/06, Josef Svenningsson [EMAIL PROTECTED] wrote:
On 3/1/06, Tommy Pettersson [EMAIL PROTECTED] wrote:
Without much surprise, here comes darcs 1.0.6, very much
identical to 1.0.6rc1.
snip
New features:
lots of new nice feautures presented
I just have a question about the
11 matches
Mail list logo
