My favorites | Sign in
Project Home Issues
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 2458: 2.3.0 to 2.3.1 broke things, need better versioning and less churn
1 person starred this issue and may be notified of changes. Back to list
Status:  Invalid
Owner:  ----
Closed:  Mar 2015


Sign in to add a comment
 
Reported by dchurch...@gmail.com, Mar 10, 2015
This is more of a complaint for arshaw than anything. The amount of churn in this library is ridiculous.

Upgrading from 2.3.0 to 2.3.1 added "12a" after every event until I added a addDayDefault setting. This shouldn't happen. Deprecated functionality should not disappear when a patch version increments.

Even the docs section on fullcalendar.io changes too often to be authoritative.

Please use the following convention for your versioning scheme:

major.minor[.maintenance[.build]]


Mar 11, 2015
Project Member #1 adamrs...@gmail.com
There was no intended behavior change with allDayDefault between these two version. It was a maintenance release. Demonstrate the difference in behavior you are experience with two different reduces test cases. Follow the directions here:

http://fullcalendar.io/wiki/Reporting-Bugs/

After you do that, we can address this ridiculousness.

PS- will reopen this ticket once you post demo
Status: Invalid
Labels: Type-Bug
Sign in to add a comment

Powered by Google Project Hosting