Launcher Release Inconsistencies

[spinachlancaster]

They're maddening!

So the launcher tells me that 1.4.7 was released recently: Great! Except it doesn't show up here:

http://www.creeperrepo.net/FTB2/maven/net/ftb/FTB_Launcher/maven-metadata.xml
http://www.creeperrepo.net/FTB2/maven/net/ftb/FTB_Launcher/
http://new.creeperrepo.net/FTB2/static/newversion.xml
http://www.creeperrepo.net/FTB2/static/version.xml

Which is where new versions usually end up.

The Github project does not utilize the 'release' function, so I can't look there.

The 'News' portion of the main site never mentions version increments, and the 'Recent Changes' section of the Launcher never has it either. In fact, it currently has 10407 as the current version!

All in all, this is a big headache: Why are there so many different avenues of getting wrong or outdated information?

 

[Watchful11]

See
http://ftb.cursecdn.com/FTB2/static/newversion.xml
and
http://ftb.cursecdn.com/FTB2/maven/net/ftb/FTB_Launcher/maven-metadata.xml

As well as
http://www.feed-the-beast.com/launcher/change-log

 

[spinachlancaster]

See
http://ftb.cursecdn.com/FTB2/static/newversion.xml
and
http://ftb.cursecdn.com/FTB2/maven/net/ftb/FTB_Launcher/maven-metadata.xml

As well as
http://www.feed-the-beast.com/launcher/change-log

Hey, thanks! Mayhaps it would be best to take down the older pages.
The change-log is also never really helpful because it's sporadically updated and never has the minor version numbers.


Thanks again!

 

[progwml6]

regarding the version listed on the changelog page as 10407.. that is 1.4.7 encoded as a number and is an artifact of older launcher versions and is used to keep compatibility

 

[jikuja]

Partially fixed now. Problems with unsynced servers. Proper fix pending.