Can We Get A Push Sticky?

[tunescool]

can we have a sticky where when theres a push and something has been added or theres a new variable thats not added to our templates we can look and see whats been added. nobody knows when things have been added, threads are started all the time asking where features are. most people would have no idea what to add to their templates anyway, have an instruction of where to put the things added

[Stinky666]

tunescool, I wouldn't hold your breath, unfortunately.
I've mentioned this (more than one time I think) before, and it's always been the same response.
There's too much stuff in a push for them to list, and pushes are happening all the time.

I think as well, when they did do something similar, not many people read the threads so it was a waste of time for them.
However, I do agree still with you. I even asked if it could just be the relevant things, but if I remember correctly, even that was argued because of the fact that what's relevant/important to one/some, wont be to others.

[tunescool]

alrite if thats the way it is, thanks stinky

[Michael]

Mar 28, 2013 12:59:18 GMT -8 Stinky666 said:

tunescool, I wouldn't hold your breath, unfortunately.
I've mentioned this (more than one time I think) before, and it's always been the same response.
There's too much stuff in a push for them to list, and pushes are happening all the time.

I think as well, when they did do something similar, not many people read the threads so it was a waste of time for them.
However, I do agree still with you. I even asked if it could just be the relevant things, but if I remember correctly, even that was argued because of the fact that what's relevant/important to one/some, wont be to others.

Yes to everything you said here. The pushes are frequent and contain a lot of changes. It would be a lot of effort to document and post this when almost nobody has paid attention to this in the past, and probably wont in the future.

[Chris]

Mar 28, 2013 13:32:55 GMT -8 Michael said:

...and probably wont in the future.

Probably not the minutiae but some sort of public posting of any upcoming broad stroke changes would promote a more proactive development community rather than that reactionary mad dash to fix something when half the codes in the database breaks due to a change made by Proboards. Rapid change is to be expected during beta so not a priority but there should be some sort of notification system put in place once the software goes gold.

I would venture that such chaotic events don't reflect well on Proboards especially when it can be easily mitigated

[Michael]

Mar 28, 2013 19:51:35 GMT -8 Chris said:

Mar 28, 2013 13:32:55 GMT -8 Michael said:

...and probably wont in the future.

Probably not the minutiae but some sort of public posting of any upcoming broad stroke changes would promote a more proactive development community rather than that reactionary mad dash to fix something when half the codes in the database breaks due to a change made by Proboards. Rapid change is to be expected during beta so not a priority but there should be some sort of notification system put in place once the software goes gold.

I would venture that such chaotic events don't reflect well on Proboards especially when it can be easily mitigated

This is entirely dependent on how we decide to do CSS and template changes in the future. More likely is that we'll opt for the least-destructive or non-destructive way of merging changes in as possible, with the option for you either just apply all of them, or review them. This has not yet been decided on. 

Our aim is to make designing and programming in v5 as easy as possible, both for developers, and end users.