On Tue, 2008-12-09 at 15:19 -0600, Kevin Day wrote:
[ Other points were not ignored, just nothing to really say about them
other than Yes and/or Will try, etc. ]
* More notice to hubs@ before the release notes are generated. The
releases always come with a At the time of this writing, these
Ken Smith wrote:
With the 7.0 release I tried giving just the URL
of the primary site (ftp.freebsd.org) but that proved people don't just
want easy - they're lazy. For the most part they just clicked on that
and didn't look around for a mirror. Hence your observation about the
difference in
* Patrick Lamaizière ([EMAIL PROTECTED]) wrote:
Ruben van Staveren [EMAIL PROTECTED] a écrit :
Though experimental, I'm greatly enjoying
http://www.secnetix.de/olli/FreeBSD/svnews/?p=/stable/7
Nice. There is also http://freshbsd.org/ (really cool IMHO).
Thanks; I write/run that. I'm
On 9 Dec 2008, at 10:56, Aristedes Maniatis wrote:
Sure, but show me how to go to http://svn.freebsd.org/viewvc/base/
and see commit log per branch or any other way to see what is going
on in a branch. Fisheye gives you that in a really clear way and it
costs nothing to add another option
On 09/12/2008, at 5:21 AM, Peter Jeremy wrote:
What do you mean as news source? Commits are inherently low level
and it's difficult to see how a commit could be massaged into some
sort of press release without a fair amount of meta information in
the commit log.
Well, I use this as a way of
Le Tue, 9 Dec 2008 11:16:57 +0100,
Ruben van Staveren [EMAIL PROTECTED] a écrit :
Sure, but show me how to go to http://svn.freebsd.org/viewvc/base/
and see commit log per branch or any other way to see what is
going on in a branch. Fisheye gives you that in a really clear way
and it
On Dec 8, 2008, at 10:25 AM, Ken Smith wrote:
Bottom line is my communication skills suck and of the bazillion other
things I could do with my time these sorts of housekeeping chores wind
up at a low enough priority they don't get done. But as you and
others
have made clear the priority
I've resisted sending this email for a while since I really don't want
to start a bikeshed nor a flame. However there comes a time to express
my thoughts over the lack of visibility of the release process for
FreeBSD 7.1. Here are the resources I am aware of:
* release timeline [1
On Mon, 2008-12-08 at 20:57 +1100, Aristedes Maniatis wrote:
I've resisted sending this email for a while since I really don't want
to start a bikeshed nor a flame. However there comes a time to express
my thoughts over the lack of visibility of the release process for
FreeBSD 7.1. Here
On 2008-Dec-08 20:57:37 +1100, Aristedes Maniatis [EMAIL PROTECTED] wrote:
* subversion. Without checking out the whole repository, it is a
little hard to use this as a news source and emails to the commit list
still look more like cvs than svn so it is a bit hard to see which
branch commits
Ken Smith wrote:
On Mon, 2008-12-08 at 20:57 +1100, Aristedes Maniatis wrote:
I've resisted sending this email for a while since I really don't want
to start a bikeshed nor a flame. However there comes a time to express
my thoughts over the lack of visibility of the release process
I'd also appreciate a little more frequent updating of the release
schedule, maybe with some terse we're waiting on this ... notes,
like there were for some past releases. I'd guess the amount of time
involved in doing so would be modest.
* subversion. Without checking out the whole repository,
On Mon, Dec 08, 2008 at 08:57:37PM +1100, Aristedes Maniatis wrote:
3. Improvements to the bug tracker. Personally I'd love to see
something like Jira used [4] with all the sophistication of workflow,
release notes, voting for bugs, etc, etc.
I have some notes for some prototyping ideas,
13 matches
Mail list logo
