Maybe they are preparing for some huge update, who knows, since app is still used by many developers and forums are pretty active 🙂
Is wyBuild dead? (Answer: No).
No wyBuild isn't dead. We're working on releasing the next version.
paulCan I ask what is the version number of next release?
Is it a good time to buy it now or better to wait a bit for new release?
Can I ask what is the version number of next release?
2.8
Is it a good time to buy it now or better to wait a bit for new release?
We won't be releasing a "major" version (that is, 3.0) for quite a while (more than a year). And even when we do release 3.0 we won't leave recent purchasers out in the cold.
Event though 2.8 isn't a "major" version (that is, it's a free update for existing customers), it contains major feature additions.
Short answer: yes, it's a good time to buy.
jmelhusHi,
What is the approximate release date for the next wyBuild version you are referring to here? A week, month, year? Would this version be better integrated with Wix?
Br
Jgen
Hey Jgen,
Would this version be better integrated with Wix?
Yes.
Hi,
are there any news on the wyBuild v2.8 release date?
ThanksStefan
Hey Stefan,
It's coming.
OK.
We're not giving a hard release date because there are a number of large feature additions. It's being worked on and it will be out when it's out.
> "We're not giving a hard release date because there are a number of large feature additions.> It's being worked on and it will be out when it's out."
Sorry my friend, but this is a mistake. There is just so much historical evidence against this attitude, a few examples:
- http://www.neilgunton.com/doc/?o=1&doc_id=8583- http://chadfowler.com/blog/2006/12/27/the-big-rewrite/- http://www.joelonsoftware.com/articles/fog0000000069.html- http://en.wikipedia.org/wiki/Agile_software_development- http://en.wikipedia.org/wiki/Vaporware
You are a single guy with a relatively small code base, so I don't doubt that you can dig yourself out of whatever hole you got into (that suddenly took us from a roughly monthly release schedule to going on TWO YEARS with no update). But during this time you have shaken your customers' confidence, inflicted a huge diff of unknown bugs and behavioral changes on upgraders, and possibly risked "Osborne effect" for new customers (as suggested in this thread).
And why? I've seen it many times before, and I can guess exactly what you're thinking. "I'm making some huge important change that has to be done all at once. It's a lot of work, but it's worth it. The ends will justify the means!"
This is a myth. The whole insight of the various modern agile development methodologies is that EVERY project can be broken down into small incremental releases. It's not always obvious how to do this, but it is always possible, and it is always better. Release early, release often, and build your business around customer feedback, not software architecture.
We've covered this in other threads on this forum. We've released 2.7 to beta testers, found the installer integration didn't work as smoothly as planned, replaced it with another installation system and we're preparing the release of 2.8.
The 2.7/2.8 releases were always planned to be large releases. Not a re-write but rather feature additions. The large majority of *existing* code is unchanged.
We're comfortable doing this because the handful of bugs in 2.6.x have known workarounds.
So, to re-iterate: it'll be out when it's out. We're just as anxious to get it out as our customers are to get it.
Any update or news on the release schedule for 2.8 ? We have been previously informed (in January) that this might be out in 2 months time but there has been no news on this since. We are just wondering where things stand, We have a number of products that successfully use wyupdate but we also have some of products where we would like to use wyupdate but due to their user selectable install options and possible combinations of exe (including windows services) and dll modules updating has proven to be far too difficult and so we have held off attempting to implement automatic updates for these. This is something we have held back on in the hope that future version of wybuild would make life easier for us. Now with the lack of any updates on the wybuild release status we are about to re-evaluate our options. Any information would be most welcome!
It's being worked on and we look forward to its release.
KCTHi Wyatt,
I've just evaluated wyBuild for our company and you did a really grat job. Most of our requirements are met. It wasn't on our screen as the first thing every big company will look for is how old it the last version. It is cruitial that you get bugfixes quite soon in case you get problems. Although in you case the software works quite well. Better than expected for an "old" software. You big bonus is that you answer questions quite fast here in the forum that indicates that it is still active. So that's the problem it is really good but you do not see progress. As many others I really like to know when the next release will come out. I know "it's done when it's done" 🙂 If the quality is as high it might be the right way in case that it is not possible to ship those features one by one. You just get the impression that nothing will happen ever so you will loose trust.Maybe you can add a small update log next to the download section where you post status updates. Added this, problems with that etc. This will show that there is progress with a current time stamp. So you will get customers attention more easily and will not loose trust.Another option is to change you business model if you like. There are many good projects that are open source (as you update) where the community can help and you earn money with support etc. I think many would love to help.But these are just suggestions as my intention is that this project will not stop to exist. It can really have a great future. So happy codingKCT
Alex SilvaHi Wyatt,
I've just evaluated wyBuild for our company and you did a really grat job. Most of our requirements are met. It wasn't on our screen as the first thing every big company will look for is how old it the last version. It is cruitial that you get bugfixes quite soon in case you get problems. Although in you case the software works quite well. Better than expected for an "old" software. You big bonus is that you answer questions quite fast here in the forum that indicates that it is still active. So that's the problem it is really good but you do not see progress. As many others I really like to know when the next release will come out. I know "it's done when it's done" 🙂 If the quality is as high it might be the right way in case that it is not possible to ship those features one by one. You just get the impression that nothing will happen ever so you will loose trust.Maybe you can add a small update log next to the download section where you post status updates. Added this, problems with that etc. This will show that there is progress with a current time stamp. So you will get customers attention more easily and will not loose trust.Another option is to change you business model if you like. There are many good projects that are open source (as you update) where the community can help and you earn money with support etc. I think many would love to help.But these are just suggestions as my intention is that this project will not stop to exist. It can really have a great future. So happy codingKCT
+1 👽
Another option is to change you business model if you like. There are many good projects that are open source (as you update) where the community can help and you earn money with support etc. I think many would love to help.
The parts you include with your app (wyUpdate & AutomaticUpdater) are already open source. It's not a viable business model to open source wyBuild.
But these are just suggestions as my intention is that this project will not stop to exist. It can really have a great future.
Yep, we're working hard on it.
SdBI vote against monthly releases with new Features for tooling Software just to keep customers happy. As this Piece of Software is a tool to produce other Software products I won't update every month as this would require me to run the complex process of testing. For a regular application it is OK to publish Releases in a short interval. Would you update your development Environment every month if MS would publish VS2014.1, VS2014.2 and so forth ? I doubt it. You want to deliver Quality Software an this occasionally requires intensive testing.
If the Statement is correct that the new wyBuild will support WIX then I understand the Long time for a new release, because there are many important decisions to be made for the new Version. You won't publish a Version and lateron regret a design decision and have a Support nightmare. As you pointed out the Company might be run by only one Person. Then development and testing is not done in a rapid manner.
I agree that small fixes can be published in a shorter regular interval.
So as a final Statement I say, wyDay please Support us with shorter release cycles for bug fixes and please take your time for a new Version with big changes in functionality.
Best regards,Stefan
> "We're not giving a hard release date because there are a number of large feature additions.> It's being worked on and it will be out when it's out."
Sorry my friend, but this is a mistake. There is just so much historical evidence against this attitude, a few examples:
- http://www.neilgunton.com/doc/?o=1&doc_id=8583- http://chadfowler.com/blog/2006/12/27/the-big-rewrite/- http://www.joelonsoftware.com/articles/fog0000000069.html- http://en.wikipedia.org/wiki/Agile_software_development- http://en.wikipedia.org/wiki/Vaporware
You are a single guy with a relatively small code base, so I don't doubt that you can dig yourself out of whatever hole you got into (that suddenly took us from a roughly monthly release schedule to going on TWO YEARS with no update). But during this time you have shaken your customers' confidence, inflicted a huge diff of unknown bugs and behavioral changes on upgraders, and possibly risked "Osborne effect" for new customers (as suggested in this thread).
And why? I've seen it many times before, and I can guess exactly what you're thinking. "I'm making some huge important change that has to be done all at once. It's a lot of work, but it's worth it. The ends will justify the means!"
This is a myth. The whole insight of the various modern agile development methodologies is that EVERY project can be broken down into small incremental releases. It's not always obvious how to do this, but it is always possible, and it is always better. Release early, release often, and build your business around customer feedback, not software architecture.