YAFLogo

Thantis
  • Thantis
  • 81.8% (Honored)
  • YAF Commander Topic Starter
12 years ago
I have noticed lately that a lot of folks are wary of compiling source, would a nightly, or weekly, build be a possible option?

This would allow those who are gun shy of source code to still get more recent changes if they wish. Of course, those same people would still have to realize these are pre-release versions and subject to the typical problems that come with pre-release code.

Sponsor
tha_watcha
  • tha_watcha
  • 100% (Exalted)
  • YAF.NET Project Lead 🤴 YAF Version: 4.0.1 BETA
12 years ago

I have noticed lately that a lot of folks are wary of compiling source, would a nightly, or weekly, build be a possible option?

This would allow those who are gun shy of source code to still get more recent changes if they wish. Of course, those same people would still have to realize these are pre-release versions and subject to the typical problems that come with pre-release code.

Originally Posted by: Thantis 

The problem is not providing nightly builds, but to support. It wouldnt be easy to support all builds. I also think those people that are aware of prerelease versions but still want to use those version in real live websites know how to build the source code and apply fixes quickly. For inexpirienced users it would be realy bad to install an nightly build that breaks the whole site and then they have to wait until a new buil is published.

I uploaded an updated build script today, where you can compile the yaf source without visual studio, that's the quick solution but maybe we could make a test week with automated nightly build to see how that goes.

squirrel
12 years ago

I have noticed lately that a lot of folks are wary of compiling source, would a nightly, or weekly, build be a possible option?

This would allow those who are gun shy of source code to still get more recent changes if they wish. Of course, those same people would still have to realize these are pre-release versions and subject to the typical problems that come with pre-release code.

Originally Posted by: tha_watcha 

The problem is not providing nightly builds, but to support. It wouldnt be easy to support all builds. I also think those people that are aware of prerelease versions but still want to use those version in real live websites know how to build the source code and apply fixes quickly. For inexpirienced users it would be realy bad to install an nightly build that breaks the whole site and then they have to wait until a new buil is published.

I uploaded an updated build script today, where you can compile the yaf source without visual studio, that's the quick solution but maybe we could make a test week with automated nightly build to see how that goes.

Originally Posted by: Thantis 

I'd be willing to contribute 'builds' and hosting for them if needed. I have no problems pulling YAF source from codeplex and running builds --


If you can't find it using the forum search, try my signature link -- searches this site using Google: Google is my Friend 
squirrel
12 years ago
But like tha_watcha said -- it would have to be unsupported - and that's for YAF only -- I don't run a portal so I wouldn't be building 'portal modules' or anything like that (but would host if needed) --
If you can't find it using the forum search, try my signature link -- searches this site using Google: Google is my Friend 
Thantis
  • Thantis
  • 81.8% (Honored)
  • YAF Commander Topic Starter
12 years ago
I agree, they would need to be unsupported, it would also need to be clearly spelled out that they aren't supported. Probably in giant red flashing letters for those who don't read. 🙂 Though you have a point, most people who are ready for dealing with pre-release code know how to compile it.
squirrel
12 years ago

I agree, they would need to be unsupported, it would also need to be clearly spelled out that they aren't supported. Probably in giant red flashing letters for those who don't read. 🙂 Though you have a point, most people who are ready for dealing with pre-release code know how to compile it.

Originally Posted by: Thantis 

In some aspects they can compile, but in some instances, while they might be ready for the bleeding edge, they might not know how to get there. The disclaimer needs to read that anyone running 'these builds' is subject to NO support, including paid, because they are not official releases. It also needs to make the point about 'backups' and not being able to 'roll backwards' the database should something go wrong. Not for use in production servers, etc...

I'm up for building weeklys and hosting them - that's no problem. Nightly I wouldn't be able to keep up with but otherwise I could cover that end... I've got the servers and the space to host em...


If you can't find it using the forum search, try my signature link -- searches this site using Google: Google is my Friend 
tha_watcha
  • tha_watcha
  • 100% (Exalted)
  • YAF.NET Project Lead 🤴 YAF Version: 4.0.1 BETA
12 years ago

I agree, they would need to be unsupported, it would also need to be clearly spelled out that they aren't supported. Probably in giant red flashing letters for those who don't read. 🙂 Though you have a point, most people who are ready for dealing with pre-release code know how to compile it.

Originally Posted by: squirrel 

In some aspects they can compile, but in some instances, while they might be ready for the bleeding edge, they might not know how to get there. The disclaimer needs to read that anyone running 'these builds' is subject to NO support, including paid, because they are not official releases. It also needs to make the point about 'backups' and not being able to 'roll backwards' the database should something go wrong. Not for use in production servers, etc...

I'm up for building weeklys and hosting them - that's no problem. Nightly I wouldn't be able to keep up with but otherwise I could cover that end... I've got the servers and the space to host em...

Originally Posted by: Thantis 

Maybe we could use an CI Server that builds and publishes automatically, i could install that on my server.

squirrel
12 years ago

I agree, they would need to be unsupported, it would also need to be clearly spelled out that they aren't supported. Probably in giant red flashing letters for those who don't read. 🙂 Though you have a point, most people who are ready for dealing with pre-release code know how to compile it.

Originally Posted by: tha_watcha 

In some aspects they can compile, but in some instances, while they might be ready for the bleeding edge, they might not know how to get there. The disclaimer needs to read that anyone running 'these builds' is subject to NO support, including paid, because they are not official releases. It also needs to make the point about 'backups' and not being able to 'roll backwards' the database should something go wrong. Not for use in production servers, etc...

I'm up for building weeklys and hosting them - that's no problem. Nightly I wouldn't be able to keep up with but otherwise I could cover that end... I've got the servers and the space to host em...

Originally Posted by: squirrel 

Maybe we could use an CI Server that builds and publishes automatically, i could install that on my server.

Originally Posted by: Thantis 

Whichever works for everyone. Since I own my own servers as well, if we need custom stuff, let me know -- :)


If you can't find it using the forum search, try my signature link -- searches this site using Google: Google is my Friend 
Jaben
  • Jaben
  • 100% (Exalted)
  • YAF Developer
12 years ago
I'm rolling out an upgraded colocation server for my/YAF.NET hosting in the next week. It has dual SSD drives and 16 GBs of ram dual QUAD core CPUs. Will finally have the "room" for a build server. I'll keep everyone updated.