> as described above, only people contributing to an artifact were notified,
> hence i never got anything neither one of you if somebody else created the
> artifact and you did not actually comment it.
yes, thats a bit an issue - and in that case it seems to be better to
have the devel list no
On 30.12.2011 18:27, Michaël Michaud wrote:
> Le 30/12/2011 17:01, Stefan Steiniger a écrit :
>> Hei Michael,
>
> Hi Stefan, Ede,
>
> I thing anybody can monitor the bug tracker... or do I get e-mail only
> because I have admin right ?
no.. until now you were _only_ notified if you have created o
Hi,
Thanks for explanation. Hope we'll get some other feedback on this subject.
*Save datasets* : I see no particular reason to have this button here
as it will save "any" modification, not just attribute modifications
and not just modifications made on active AttributePanel
*Undo/redo* : sa
Hi,
I was not exactly testing the bug tracker mail report. Just cleaning the
feature-request list.
Ede was testing how to redirect bug/feature-request reports to JPP-Devel
list.
But my opinion is the same as yours : jump-devel list and svn-notify are
enough. Moreover, I thing you can
monito
I can see that Michael is testing the bug mail report.
After two tests I would like to change my opinion. I think
that jump-pilot-svn-notify list would be the best place for this tool -
to avoid inflating the devel list ;-)
Peppe
Da: SourceForge.net
A: Sourc
Feature Requests item #3439863, was opened at 2011-11-18 03:16
Message generated for change (Settings changed) made by michaudm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=679909&aid=3439863&group_id=118054
Please note that this message will contain a full copy
Feature Requests item #3441294, was opened at 2011-11-22 19:16
Message generated for change (Settings changed) made by michaudm
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=679909&aid=3441294&group_id=118054
Please note that this message will contain a full copy
Hi Stefan,
this seems to me a good way to watch if a bug is solved.
I didn't know we have a jump-pilot-svn-notify list! There are always things to
know from Openjump.
I think that we don't have to use another list but this one (devel-user)
or jump-pilot-svn-notify list
Peppe
_
Hei all,
the previous email was a test.
We are experimenting on sending change messages to bugs automatically to
an email list.
Now the big question:
should we use this devel list? or rather a new list?
(we actually have a jump-pilot-svn-notify list, that could be abused?)
stefan
Am 30.12.11
Bugs item #3439132, was opened at 2011-11-16 18:56
Message generated for change (Settings changed) made by edso
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=679906&aid=3439132&group_id=118054
Please note that this message will contain a full copy of the comment t
Hi Michael, Stefan and other
I will answer for my modifications and the reasons why I did this modification.
Save datasets : I see no particular reason to have this button here as it will
save "any" modification, not just attribute modifications and not just
modifications made on active Attribu
11 matches
Mail list logo