Thinking it? I've got it on my 'Scheduled' area! I'm hoping they
finally fixed the sort by date function for Next and Waiting. Seems
like they should get what isn't working in N2 (that was working in
N1) fixed first.. before they address new features and/or
functionality.
I am just hopeful....they did say on their blog that the move to
the new servers earlier than planned put them behind a couple of
days in terms of further development.
Guess we will see....it still would be great to see some new
things and remaining bugs fixed...
I figured you would have a count down counter on your desktop
holding Nirvana to their "2 weeks between releases" claim. LOL
I don't know about you guys, but I am really starting to need
attachment support. Many of my Projects/Task lately have required
attachments and my current hack is starting to get old. :-)
Yeah...trying to be flexible here. I just love Nirvana so much
that I am always so anxious about them catching up with their
competition.
I agree about the attachments. I get so much work by email with
attached documents. I would love to be able to forward them to my
Nirvana inbox. Plus, being able to add attachments to other tasks
would be great.
I would also love for embedded images on the Task notes. Some of
my emails have a picture that is embedded and not an actual file. I
would love for the embedded pictures to also show up in Nirvana
when I forward the email to my inbox.
:-)
Sorry for derailing the topic a little.
Let's just hope for Recurring task make it in the next release
and take baby steps to the other features we want.
11 Posted by David Johnson on 04 Mar, 2011 11:51 PM
If I read the latest blog post correctly is sounds like we may not see an update today :(
David
-----Original Message-----
From: Proximo [mailto:***@tenderapp.com]
Sent: Friday, March 04, 2011 14:51
To: David Johnson
Subject: Re: Next release today? [General Chit Chat]
For me, fortnightly releases are meant to happen no matter what
- i.e. despite problems, it's a way of delivering software.
I interpreted the communication to be 'there will be a
fortnightly release' - not 'we will try and release fortnightly'.
The former is something you can rely on, plan for and get excited
about - the latter is no change to what we've had since N2 came
out.........
I thought I could not live with out attachments but now I kind
of like it ...keeps Nirvana Simpler and cleaner. By using Evernote
as my project folders and Nirvana just for next actions not
reference material I am kind of liking it.
I'm sure everyone has their own priority list. Mine is:
E-mail reminders;
Tag cloud
Evernote integration
I know I'm really in the minority, here, but I honestly don't
care about recurring tasks. When I complete a task that's going to
be done again ... I simply push back the due date instead of
marking it as complete.
To quote the above link:
"The third goal is about taking the pressure off software engineers
to finish features in a single release cycle. Under the old model,
when we faced a deadline with an incomplete feature, we had three
options, all undesirable: (1) Engineers had to rush or work
overtime to complete the feature by the deadline, (2) We delayed
the release to complete that feature (which affected other
un-related features), or (3) The feature was disabled and had to
wait approximately 3 months for the next release. With the new
schedule, if a given feature is not complete, it will simply ride
on the the next release train when it’s ready. Since those
trains come quickly and regularly (every six weeks), there is less
stress."
If a statement is made that a release will be made every 2 weeks
then a release should be made every 2 weeks.
If a feature isn't ready for that release then fair enough, it's
only 2 weeks for the next release but the 2 weekly release cycle
should be honored and whatever code changes have been put back in
the last 2 weeks get pushed to the users.
I work for a CADCAM software company and we push monthly updates
out because that's our promise to our customers through our SLA
with them and that happens regardless of whether a particular
feature has made it through to the release codebase.
I hope I don't come across as overly critical as I think Nirvana
is a great product and comparing your development resources to
Googles' is quite unfair but I think users would be more
understanding on not seeing a particular feature make a release if
they knew that another release was coming in 2 weeks.
In your particular development environment I do think a "small but
often" release cycle would definitely help keep the natives
happy.
Not critical of anyone's comments here, at all ... but just
pointing out that the discussion board apparently allows multiple
people to lay claim to the same user name! (Maybe the
capitalization difference is enough in the software's mind.) That
has the potential to be confusing ...
2 Posted by candeshouse on 04 Mar, 2011 05:05 PM
I'm glad I wasn't the only person thinking it...was hoping for recurring tasks today, among other things. ; )
3 Posted by Ken on 04 Mar, 2011 05:25 PM
Thinking it? I've got it on my 'Scheduled' area! I'm hoping they finally fixed the sort by date function for Next and Waiting. Seems like they should get what isn't working in N2 (that was working in N1) fixed first.. before they address new features and/or functionality.
4 Posted by Kenny Grant on 04 Mar, 2011 05:30 PM
I'm refreshing N2 every .001 milliseconds
5 Posted by david-drake on 04 Mar, 2011 06:50 PM
Kenny....why such a long interval between refreshing? :))
-David
6 Posted by Kenny Grant on 04 Mar, 2011 08:17 PM
ha ha, yes I must try harder David.
I should be more honest and state that I'm expecting a release - as opposed to hoping for one. I'm sure I won't be dissapointed.
7 Posted by david-drake on 04 Mar, 2011 08:22 PM
I am just hopeful....they did say on their blog that the move to the new servers earlier than planned put them behind a couple of days in terms of further development.
Guess we will see....it still would be great to see some new things and remaining bugs fixed...
-David
8 Posted by Proximo on 04 Mar, 2011 10:35 PM
@David,
I figured you would have a count down counter on your desktop holding Nirvana to their "2 weeks between releases" claim. LOL
I don't know about you guys, but I am really starting to need attachment support. Many of my Projects/Task lately have required attachments and my current hack is starting to get old. :-)
9 Posted by david-drake on 04 Mar, 2011 10:45 PM
Hi Proximo,
Yeah...trying to be flexible here. I just love Nirvana so much that I am always so anxious about them catching up with their competition.
I agree about the attachments. I get so much work by email with attached documents. I would love to be able to forward them to my Nirvana inbox. Plus, being able to add attachments to other tasks would be great.
-David
10 Posted by Proximo on 04 Mar, 2011 10:50 PM
I would also love for embedded images on the Task notes. Some of my emails have a picture that is embedded and not an actual file. I would love for the embedded pictures to also show up in Nirvana when I forward the email to my inbox.
:-)
Sorry for derailing the topic a little.
Let's just hope for Recurring task make it in the next release and take baby steps to the other features we want.
11 Posted by David Johnson on 04 Mar, 2011 11:51 PM
If I read the latest blog post correctly is sounds like we may not see an update today :(
David
-----Original Message-----
From: Proximo [mailto:***@tenderapp.com]
Sent: Friday, March 04, 2011 14:51
To: David Johnson
Subject: Re: Next release today? [General Chit Chat]
12 Posted by Proximo on 05 Mar, 2011 01:24 AM
REVOLT!
I will start the Facebook Nirvana Revolt page. Someone else provide the torches.
13 Posted by Kenny Grant on 07 Mar, 2011 09:10 AM
Disappointing.
For me, fortnightly releases are meant to happen no matter what - i.e. despite problems, it's a way of delivering software.
I interpreted the communication to be 'there will be a fortnightly release' - not 'we will try and release fortnightly'. The former is something you can rely on, plan for and get excited about - the latter is no change to what we've had since N2 came out.........
14 Posted by diane on 07 Mar, 2011 05:32 PM
I thought I could not live with out attachments but now I kind of like it ...keeps Nirvana Simpler and cleaner. By using Evernote as my project folders and Nirvana just for next actions not reference material I am kind of liking it.
15 Posted by diane on 07 Mar, 2011 06:03 PM
and for me email contact info in waiting is a much bigger priority.
16 Posted by Mark on 07 Mar, 2011 06:51 PM
I'm sure everyone has their own priority list. Mine is:
I know I'm really in the minority, here, but I honestly don't care about recurring tasks. When I complete a task that's going to be done again ... I simply push back the due date instead of marking it as complete.
17 Posted by Mark S on 08 Mar, 2011 03:22 PM
@Kenny Grant +1
I like the way Google pushes its updates to Chrome on a regular schedule regardless.
http://blog.chromium.org/2010/07/release-early-release-often.html
To quote the above link:
"The third goal is about taking the pressure off software engineers to finish features in a single release cycle. Under the old model, when we faced a deadline with an incomplete feature, we had three options, all undesirable: (1) Engineers had to rush or work overtime to complete the feature by the deadline, (2) We delayed the release to complete that feature (which affected other un-related features), or (3) The feature was disabled and had to wait approximately 3 months for the next release. With the new schedule, if a given feature is not complete, it will simply ride on the the next release train when it’s ready. Since those trains come quickly and regularly (every six weeks), there is less stress."
If a statement is made that a release will be made every 2 weeks then a release should be made every 2 weeks.
If a feature isn't ready for that release then fair enough, it's only 2 weeks for the next release but the 2 weekly release cycle should be honored and whatever code changes have been put back in the last 2 weeks get pushed to the users.
I work for a CADCAM software company and we push monthly updates out because that's our promise to our customers through our SLA with them and that happens regardless of whether a particular feature has made it through to the release codebase.
I hope I don't come across as overly critical as I think Nirvana is a great product and comparing your development resources to Googles' is quite unfair but I think users would be more understanding on not seeing a particular feature make a release if they knew that another release was coming in 2 weeks.
In your particular development environment I do think a "small but often" release cycle would definitely help keep the natives happy.
Thanks,
Mark
18 Posted by Mark on 08 Mar, 2011 03:29 PM
Not critical of anyone's comments here, at all ... but just pointing out that the discussion board apparently allows multiple people to lay claim to the same user name! (Maybe the capitalization difference is enough in the software's mind.) That has the potential to be confusing ...
19 Posted by Mark S on 08 Mar, 2011 03:32 PM
What?
Hey, I never said that?
What's going on here...
:)
20 Posted by Mark S on 08 Mar, 2011 03:33 PM
Anyway, duly changed.
Thanks.
21 Posted by Mark on 08 Mar, 2011 04:17 PM
Wow, it's like looking in a mirror ... :)
22 Posted by Proximo on 08 Mar, 2011 07:35 PM
I understand everyone point here but I just wanted to make sure one thing is clear.
I WAS ONLY KIDDING WHEN I SAID "REVOLT".
Just wanted to point that out. :-)
By the time I checked this discussion again, it seems like a Revolt was taking place and I DON't want to take credit for it. ROFL
23 Posted by Mark on 08 Mar, 2011 07:37 PM
Hey, somebody has to be the ringleader! :)