On Tue, Dec 30, 2014 at 5:03 AM, W. Martin Borgert <[email protected]> wrote:
> Quoting 'Felix Schwarz' via Trac Development <[email protected]>: > >> If you can release Trac more often this means users get your fixes earlier >> > > Adding my 2 cents: I agree with Felix. > It is important, however, that stable releases do not contain many > unnessary > changes. E.g. one Trac update had a change of an e-mail address in dozens > of > files. This is fine for 1.1 but makes it harder e.g. for Debian to upgrade > the 1.0 line. > I generally try to push style changes and minimal refactorings to 1.0-stable because it reduces the possibility of merge conflicts later on when merging changes from 1.0-stable to the trunk. However, I'm interested to know how these code changes might make the process for Debian more difficult. What is the process for upgrading the 1.0 package for Debian? I have thought it was nothing more than checking out the release from the repository and creating the package. -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
