On Fri, Oct 3, 2008 at 9:42 PM, Frederik Ramm [EMAIL PROTECTED] wrote:
Enforcing the expiry or closing of changesets gives us the chance to
know for sure that certain changesets - most, actually - are complete
and will not change anymore; you can then say for sure: user so-and-so
made the
Hi devs,
Should changesets automatically be closed after a period of time? If
so how long?
Are changesets useful if they are never closed, or empty?
Should there be a way for an application to be able to query and check
to see if it has an open changeset to use, thus preventing open
(forgot to reply to list)
Hi,
Shaun McDonald wrote:
Should changesets automatically be closed after a period of time? If so
how long?
I thought that when a changeset is created and whenever something is
added, the expiration date is set to now + 30 minutes. A changeset
whose expiration date
On 3 Oct 2008, at 15:54, Frederik Ramm wrote:
(forgot to reply to list)
Hi,
Shaun McDonald wrote:
Should changesets automatically be closed after a period of time?
If so
how long?
I thought that when a changeset is created and whenever something is
added, the expiration date is set to
On Fri, Oct 3, 2008 at 4:23 PM, 80n [EMAIL PROTECTED] wrote:
On Fri, Oct 3, 2008 at 3:54 PM, Frederik Ramm [EMAIL PROTECTED] wrote:
Shaun McDonald wrote:
Should changesets automatically be closed after a period of time? If so
how long?
Why does a changeset need to even have an open/closed
On Fri, Oct 3, 2008 at 4:23 PM, 80n [EMAIL PROTECTED] wrote:
On Fri, Oct 3, 2008 at 3:54 PM, Frederik Ramm [EMAIL PROTECTED] wrote:
(forgot to reply to list)
Hi,
Shaun McDonald wrote:
Should changesets automatically be closed after a period of time? If so
how long?
Why does a
Hi,
Shaun McDonald wrote:
There is a slight issue here, because in the database table for
changesets only stores the time it was created_at (timestamp), and
whether it is open, as a boolea. It doesn't store the expiry time, nor
the time it was closed.
I thought the one that I designed did
Hi,
since changesets are not atomic, nor can they be automatically
reverted, is it useful to be able to close changesets?
I'm also in the I don't want a changeset to go on forever camp. If the
edit is so complex that it cannot be commited within a few hours then it
should not be one
On Fri, Oct 3, 2008 at 6:19 PM, Frederik Ramm [EMAIL PROTECTED] wrote:
Hi,
since changesets are not atomic, nor can they be automatically
reverted, is it useful to be able to close changesets?
I'm also in the I don't want a changeset to go on forever camp. If the
edit is so complex that
9 matches
Mail list logo
