Announcing: ZFS-fuse 0.7.0
#7 — Information files are out-of-date
| State | In progress |
|---|---|
| Version: | 0.6.0 |
| Area | Process |
| Issue type | Bug |
| Severity | Medium |
| Submitted by | Charles Huber |
| Submitted on | Dec 10, 2009 |
| Responsible | Seth Heeren |
| Target release: | 0.7.0 |
Last modified on
Sep 19, 2010
by
Seth Heeren
The following informational files are out-of-date in one way or another:
BUGS (important! :)
CHANGES
INSTALL (possibly)
README
STATUS
BUGS (important! :)
CHANGES
INSTALL (possibly)
README
STATUS
Added by
Christian Kujau
on
Jan 29, 2010 02:24 PM
Issue state:
unconfirmed → open
> BUGS (important! :)
Hopefully addressed in #15, #16.
> INSTALL (possibly)
> README
Could you be more specific, please? For the README file, there's #17 and a patch is ready.
> STATUS
> CHANGES
Not sure about these two. I'm often tempted to discard those or just put in a weblink pointing to the project homepage, where this can be updated more easily. Now with git (and good commit messages :-)) one could discard the "CHANGES" altogether, as it's all the repository anyway.
Hopefully addressed in #15, #16.
> INSTALL (possibly)
> README
Could you be more specific, please? For the README file, there's #17 and a patch is ready.
> STATUS
> CHANGES
Not sure about these two. I'm often tempted to discard those or just put in a weblink pointing to the project homepage, where this can be updated more easily. Now with git (and good commit messages :-)) one could discard the "CHANGES" altogether, as it's all the repository anyway.
Added by
Seth Heeren
on
Jan 29, 2010 02:58 PM
Issue state:
open → in-progress
Target release:
None → 0.6.1
Responsible manager:
(UNASSIGNED) → sgheeren
#15 #16 #17 pushed into critical
Thanks for the concrete contributions.
I'm strongly in favour of putting the STATUS (and so) on the website. I'm unsure yet as to 'how' but once we figure it out, I will do that to (#7, closed).
--
There is a merge upcoming from critical into master so we'll keep this issue open as sign that this should still happen.
Thanks for the concrete contributions.
I'm strongly in favour of putting the STATUS (and so) on the website. I'm unsure yet as to 'how' but once we figure it out, I will do that to (#7, closed).
--
There is a merge upcoming from critical into master so we'll keep this issue open as sign that this should still happen.
Added by
Rudd-O
on
Jan 29, 2010 03:24 PM
For the moment, before I actually set up a Gitweb, I will now create a Wiki area on the site, and put the contents of the STATUS file there. Whether to leave the STATUS file on the repo and update it twice on both site or whatever we do in the future, I leave that as a decision for the community.
Added by
Rudd-O
on
Jan 29, 2010 03:31 PM
Added by
Christian Kujau
on
Jan 30, 2010 12:49 AM
<s>OK, I've put the STATUS file on http://zfs-fuse.net/wiki/status now (which means it can be removed from the sourcetree, right?)</s> - and deleted again, see http://bit.ly/btKAJM
I somehow managed to delete the introduction text on http://zfs-fuse.net/wiki and cannot seem to restore it - sorry about that!
I somehow managed to delete the introduction text on http://zfs-fuse.net/wiki and cannot seem to restore it - sorry about that!
Added by
Seth Heeren
on
May 22, 2010 02:47 PM
Target release:
0.6.1 → 0.6.9
Keeping this one: need more tweaking for 0.6.9
Sent out a request on the list
We need to think of contrib/ and zfs-fuse.spec too in this respect
Sent out a request on the list
We need to think of contrib/ and zfs-fuse.spec too in this respect
Added by
Seth Heeren
on
Sep 19, 2010 05:54 PM
Target release:
0.6.9 → 0.7.0
Bug Hug for 0.7.0 sent
