Mailing List Archive: DAViCal: Dev

Future development & release process

Index | Next | Previous | View Threaded

andrew at morphoss

Sep 11, 2011, 4:05 PM

Post #1 of 7 (1021 views)
Permalink

Future development & release process

Hi All,

Well it's been some considerable time since the last DAViCal release,
and not really through any good reason.

There is a pre-release of 0.9.9.5 and AWL 0.47 available now at:

http://debian.mcmillan.net.nz/packages/davical/testing/

The way this has dragged on and I have lost track of where things were
up to has encouraged me to think about the process of the release and to
try and work out ways of doing things a little better.

As a start, I've added a couple of pages to the wiki:

http://wiki.davical.org/w/Release_Checklist

http://wiki.davical.org/w/Release_Planning/0.9.9.6

I would really appreciate if people could go through and add things to
those pages that you think are missing in the current procedures.

Here's hoping that by following these procedures I can get the next
release out a lot quicker than this one.

I know that some of you have some patches which I have not applied to
0.9.9.5, and I've been finding that Git *really* helps me with this. If
you have a public Git tree of DAViCal/AWL that I can pull patches from
it makes really does make it simple for me. If you can't run your own
by all means create something on Gitorious[1] or the like and work from
there.

Regards,
Andrew.

[1] http://gitorious.org/

--
------------------------------------------------------------------------
andrew (AT) morphoss (DOT) com +64(272)DEBIAN
ISO applications:
A solution in search of a problem!
------------------------------------------------------------------------

Attachments:

signature.asc (0.82 KB)

matthias.althaus at iserv

Sep 12, 2011, 1:23 AM

Post #2 of 7 (1016 views)
Permalink

Re: Future development & release process [In reply to]

Hey Andrew,

have you thought about using an issue tracker to organize the stuff? I find these much more usable than hacking stuff into a wiki. So you easily could track what to do and group issues into a release plan.

Cheers
Matthias
_______________________________________________
DAViCal-dev mailing list
DAViCal-dev [at] lists
http://lists.davical.org/listinfo/davical-dev

wolfgang at r007

Sep 12, 2011, 3:15 AM

Post #3 of 7 (1016 views)
Permalink

Re: Future development & release process [In reply to]

Hi!

Am 12.09.2011 um 10:23 schrieb Matthias Althaus:
>
> have you thought about using an issue tracker to organize the stuff? I find these much more usable than hacking stuff into a wiki. So you easily could track what to do and group issues into a release plan.

I'd second that motion. Where I work we've had very positive results drawing everything (release management, repositories, documentation, issue and feature tracking) together into such a system.
Even though at first glance it's not more expressive than what is already in place for davical (wiki, sf.net tracker, repo.or.cz), the tighter integration and well-structured-ness helps a lot.
We use Redmine, but I'm sure something similar could be achieved with Trac or other equally capable alternatives.
These tools usually give you some freedom to accommodate your workflow, which on the other hand means you have to know what your workflow is (or will be) to configure the tool accordingly. ;-)

Cheers,
--
Wolfgang Herget

_______________________________________________
DAViCal-dev mailing list
DAViCal-dev [at] lists
http://lists.davical.org/listinfo/davical-dev

andrew at morphoss

Sep 12, 2011, 8:51 PM

Post #4 of 7 (1008 views)
Permalink

Re: Future development & release process [In reply to]

On Mon, 2011-09-12 at 10:23 +0200, Matthias Althaus wrote:
> Hey Andrew,
>
> have you thought about using an issue tracker to organize the stuff? I
> find these much more usable than hacking stuff into a wiki. So you
> easily could track what to do and group issues into a release plan.

Well of course I've *thought* about issue trackers. If someone stepped
forward to help out as a release manager for DAViCal then I think it's
likely that they would want to have such a thing.

It would certainly be nice to get something to replace the current
service from Sourceforge, and I'd like to have something which can close
a bug based on me writing something into my Git commit message, or open
a bug based on me forwarding an e-mail to some automatic system.

I can write such add-ons, of course, but the platform would need to have
some kind of interface to support that kind of stuff. I suspect RT is
the one (it has a command-line client, which makes me happy :-), though
perhaps RedMine has caught up some of those features now. Or maybe
Bugzilla is also a possibility.

Meanwhile, I think I still want the wiki pages to track the next version
while perhaps we think that kind of thing through, and get something set
up.

Cheers,
Andrew.
--
------------------------------------------------------------------------
andrew (AT) morphoss (DOT) com +64(272)DEBIAN
Nietzsche is pietzsche, but Schiller is killer, and Goethe is moethe.
------------------------------------------------------------------------

Attachments:

signature.asc (0.82 KB)

matthias.althaus at iserv

Sep 13, 2011, 1:16 AM

Post #5 of 7 (1002 views)
Permalink

Re: Future development & release process [In reply to]

Hey,

> Well of course I've *thought* about issue trackers. If someone stepped
> forward to help out as a release manager for DAViCal then I think it's
> likely that they would want to have such a thing.
I was sure that you had thought about it... just wanted to get your point of view on this. ;)

I'm preferring Redmine like Wolfgang too. It's really nice and you can def link SVN/Git with it and close bugs by commits. There also should be a mail plugin or similar. I stumbled upon it in a project I was involved and adapted it for all my projects afterwards. :)

An alternative would be to move completely to Github. There you have all the Git love in one place with easy forking and you can add features like issue tracking, wiki or static pages to your repo.

Cheers
Matthias
_______________________________________________
DAViCal-dev mailing list
DAViCal-dev [at] lists
http://lists.davical.org/listinfo/davical-dev

wolfgang at r007

Sep 13, 2011, 2:05 AM

Post #6 of 7 (1009 views)
Permalink

Re: Future development & release process [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey all!

Am 13.09.2011 um 05:51 schrieb Andrew McMillan:
> On Mon, 2011-09-12 at 10:23 +0200, Matthias Althaus wrote:
>> have you thought about using an issue tracker to organize the stuff? I
>> find these much more usable than hacking stuff into a wiki.
>
> I can write such add-ons, of course, but the platform would need to have
> some kind of interface to support that kind of stuff. I suspect RT is
> the one (it has a command-line client, which makes me happy :-), though
> perhaps RedMine has caught up some of those features now.

Just a quick word on RT: Yes, it's a great issue tracker. But I've always
felt it was more geared towards helpdesk/ITIL-service-lifecycle issue
tracking. (As in, it has a big focus on reporting that is needed for ITIL
style performance evaluation, but maybe too much for software development.)
The more software-minded trackers make (e.g.) release planning much less
cumbersome.

Maybe we should collect the alternatives and properly review them.
I've taken the liberty of creating a wiki page for this purpose:

http://wiki.davical.org/w/IssueTracking

Best,
- --
Wolfgang Herget

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)

iEYEARECAAYFAk5vHOcACgkQBIDKAtYlWQaoxwCgqcoF7mD3La319/fZvZ4rsz0S
U2kAn0GRslSSCyvjOw6mIVZnfNuW/uMH
=U9w+
-----END PGP SIGNATURE-----
_______________________________________________
DAViCal-dev mailing list
DAViCal-dev [at] lists
http://lists.davical.org/listinfo/davical-dev

andrew at morphoss

Sep 13, 2011, 2:52 PM

Post #7 of 7 (998 views)
Permalink

Re: Future development & release process [In reply to]

On Tue, 2011-09-13 at 11:05 +0200, Wolfgang Herget wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hey all!
>
> Am 13.09.2011 um 05:51 schrieb Andrew McMillan:
> > On Mon, 2011-09-12 at 10:23 +0200, Matthias Althaus wrote:
> >> have you thought about using an issue tracker to organize the stuff? I
> >> find these much more usable than hacking stuff into a wiki.
> >
> > I can write such add-ons, of course, but the platform would need to have
> > some kind of interface to support that kind of stuff. I suspect RT is
> > the one (it has a command-line client, which makes me happy :-), though
> > perhaps RedMine has caught up some of those features now.
>
> Just a quick word on RT: Yes, it's a great issue tracker. But I've always
> felt it was more geared towards helpdesk/ITIL-service-lifecycle issue
> tracking. (As in, it has a big focus on reporting that is needed for ITIL
> style performance evaluation, but maybe too much for software development.)
> The more software-minded trackers make (e.g.) release planning much less
> cumbersome.

Yes, it has it's closed elements. The only big ones I can immediately
think of that *don't* have a heritage in that environment are Bugzilla
and debbugs.

> Maybe we should collect the alternatives and properly review them.
> I've taken the liberty of creating a wiki page for this purpose:
>
> http://wiki.davical.org/w/IssueTracking

Seems like a fine idea :-)

Cheers,
Andrew.

--
------------------------------------------------------------------------
andrew (AT) morphoss (DOT) com +64(272)DEBIAN
A is for Apple.
-- Hester Pryne
------------------------------------------------------------------------

Attachments:

signature.asc (0.82 KB)

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads