Hi there,
having been many years interested/active in
<https://sourceforge.net/projects/oorexx/> I have
experienced the project's switch to Allura.
The project is a long standing one, which means that the trackers have quite a
few entries and
developers have been accustomed to learning/seeing/printing code diffs right
away to make it easy to
study what got changed.
After some time of using the new system (to get accustomed to it) there are
many, many
questions/problems opened, some of which can be answered/solved on the ooRexx
developer list, some
via Allura-trackers, but it seems for very important aspects of a developer
system, there is (yet?)
no solution or knowledge available.
Therefore I would like to kindly request comments/hints/pointers to the
following three items, that
are coming into ones way, being accustomed to the old system and not having
found the counterparts
in the new Allura:
-------- Original Message --------
Subject: [Oorexx-devel] Ad Allura interface: a few questions ...
Date: Wed, 22 Aug 2012 09:50:29 +0200
From: Rony G. Flatscher
Reply-To: Open Object Rexx Developer Mailing List
<[email protected]>
To: Open Object Rexx Developer Mailing List
<[email protected]>
Sorry, if this has been answered already, just do not know the latest state.
* Ad Patches: it is possible (following Mark's directions) to subscribe
Patch messages by
merely pressing the envelope symbol on the Patch UI. However, how would
one be able to see
the patch file (the diffs) from such a message?
o One (a little bit cumbersome) way is to look in the left pane of
commits and somehow
pick the right commit from the bullet list that appears after a
while in the center
pane. However, once one gets to the diff page and tries to print
it, the printout does
not contain any of the nicely formatted code! :(
* Ad Bugs: is it possible to get the opening date, the submitter, such
that one becomes able
to sort by them as well. It is strange that the order of showing
tracker entries is from
oldest to latest, rather than the other way round (maybe the developers
only use small
databases where the order does not matter for them, but in a long
standing project one may
have hundreds, maybe more tracker entries).
* Ad svn commit diffs: it would be great, if the commit message contained
links directly to
the files that got committed with links to diffs. (The same would be
helpful for any code
submission, including the patches).
Is there anything I could do to help get the above items tackled/resolved
somehow?
---rony
Thanks in advance for any comments/hints/pointers (maybe time frames to expect
feature changes that
could help)!
N.B.: Please excuse my addressing this to allura-users and allura-dev, as I do
not know which e-mail
list is appropriate for such questions.
---rony
