• Home
  • Blog
  • Add-ons
  • Forum
  • Wiki
  • Developers
Nightingale - The tune of life, the tune of yours
  • Portal
  • Search
  • Member List
  • Calendar
  • Help
  • Portal
  • Search
  • Member List
  • Calendar
  • Help
Guest Hi, Guest
  • Login
  • Register
Login
Username:
Password: Lost Password?
 
Nightingale Forums Nightingale News & Announcements What is happening? Development

Pages (5): « Previous 1 2 3 4 5
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Thread Modes
Development
rsjtdrjgfuzkfg Offline
Developer
*******
Posts: 664
Threads: 15
Joined: Oct 2011
Reputation: 15
#41
12-20-2012, 04:21 AM
(12-19-2012, 10:29 PM)GeekShadow Wrote: I'm ok releasing and working with this branch. Maybe we can always work and release from trunk in the future... since Songbird mostly work on trunk then merge changes in branches.

I'm also for not merging everything to -1.11, however I don't think we should merge sb changes directly into a release branch because of the version numbers. Or is there some git magic for that?

However I can merge the taglib stuff if we decide to still base it on -1.11.

@GeekShadow:
Looking forward to Inno Setup Smile
Songbird/Nightingale Community Developer and German Translator
Find
Reply
ilikenwf Offline
Developer/Project Manager
*******
Posts: 412
Threads: 22
Joined: Nov 2010
Reputation: 8
#42
12-20-2012, 05:22 AM
Once we're ready to freeze, we'll tag and create a new branch... 1.12?

Then, we'll make sure none of the POTI crap is in there, Phillips Crap, etc...

from there it's just polishing and cleaning up, and building fresh deps for all platforms.

After 1.12, I say we go 2.0 because we should have xul15+ by then.
How to Build Nightingale | Nightingale on GitHub
Find
Reply
GeekShadow Offline
Mozilla addict
******
Posts: 195
Threads: 25
Joined: Nov 2010
Reputation: 4
#43
12-20-2012, 10:22 PM
So merge taglib changes in 1.11 branch with fresh deps is that ok ?
Former Songbird contributor
Nightingale Community developer
Mozilla Reps
Website Find
Reply
ilikenwf Offline
Developer/Project Manager
*******
Posts: 412
Threads: 22
Joined: Nov 2010
Reputation: 8
#44
12-21-2012, 05:08 AM
I don't see that as being a good use of time, tbh...

We can just base a 1.12 branch off of sb-trunk-oldxul and use that 1.12 branch for the release.
How to Build Nightingale | Nightingale on GitHub
Find
Reply
GeekShadow Offline
Mozilla addict
******
Posts: 195
Threads: 25
Joined: Nov 2010
Reputation: 4
#45
12-21-2012, 07:03 PM
Sounds fine Smile
Former Songbird contributor
Nightingale Community developer
Mozilla Reps
Website Find
Reply
rsjtdrjgfuzkfg Offline
Developer
*******
Posts: 664
Threads: 15
Joined: Oct 2011
Reputation: 15
#46
12-23-2012, 03:06 AM
(12-20-2012, 05:22 AM)ilikenwf Wrote: Once we're ready to freeze, we'll tag and create a new branch... 1.12?

Then, we'll make sure none of the POTI crap is in there, Phillips Crap, etc...

Agree.
Songbird/Nightingale Community Developer and German Translator
Find
Reply
« Next Oldest | Next Newest »
Pages (5): « Previous 1 2 3 4 5


  • View a Printable Version
  • Subscribe to this thread
Forum Jump:


Users browsing this thread: 1 Guest(s)
  • Return to Top
  • Lite (Archive) Mode
  • RSS Syndication
Current time: 03-22-2023, 09:56 AM Powered By MyBB, © 2002-2023 MyBB Group.
Design By AliReza_Tofighi In WhiteCrow Software Group.
white outlined nightingale project logo

Nightingale is free!
It is an Open Source project released under the terms of the GNU General Public License v2 (GPL v2).
For more details, please read the license information.

Follow us!
f  g  t

Support
  • Community Forum
  • Official Blog
  • Add-ons
  • Wiki
  • Help Forum
Contribute
  • Developer's Center
  • Translate Nightingale
  • Source Code
  • Report a Bug
Ressources
  • Download Nightingale
Linear Mode
Threaded Mode